August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-20210. ----------------------------------- Resolution: Done Released to master. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20475) Upgrade Forge Runtime to 2.19.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20475?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-20475. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 2.19.0.Final > ------------------------------------- > > Key: JBIDE-20475 > URL: https://issues.jboss.org/browse/JBIDE-20475 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-486) FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-486?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-486: -------------------------------------- merged PR > FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > --------------------------------------------------------------------- > > Key: JBTIS-486 > URL: https://issues.jboss.org/browse/JBTIS-486 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: fuse-new-licenses1.png, fuse-new-licenses2.png, fuse-new-licenses3.png > > > Please make sure that Fuse Tooling is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20475) Upgrade Forge Runtime to 2.19.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20475?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-20475: ------------------------------------ Summary: Upgrade Forge Runtime to 2.19.0.Final (was: Upgrade Forge Runtime to 2.18.1.Final) > Upgrade Forge Runtime to 2.19.0.Final > ------------------------------------- > > Key: JBIDE-20475 > URL: https://issues.jboss.org/browse/JBIDE-20475 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20529: ------------------------------------- A scan of all wildfly quickstarts found that all examples have namespace / xsd urls that are accurate. Though some are in fact redirects, the redirects are accurate and none redirect to an html page. The upstream issue for following redirects is https://bugs.eclipse.org/bugs/show_bug.cgi?id=474741 There has been no upstream response to this issue yet. > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20529: ----------------------------------- Summary: Master JIRA for XML Validation Problems Key: JBIDE-20529 URL: https://issues.jboss.org/browse/JBIDE-20529 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples, server Reporter: Rob Stryker This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-487?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-487: ----------------------------------------- [~pleacu] or [~nickboldt] any ideas on what I am missing? I'm sure it's something obvious but I can't put my finger on it. > SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------ > > Key: JBTIS-487 > URL: https://issues.jboss.org/browse/JBTIS-487 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3486) install grinder should support install of JBDS from installer, not just BYOE on Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3486?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3486: ---------------------------------- Not quite. Installer build will do an install of the contents of the installer, but NOT the contents of Central/Early Access on top of that. So... we need an install test for: * installer + Central * installer + Central + EA > install grinder should support install of JBDS from installer, not just BYOE on Eclipse > --------------------------------------------------------------------------------------- > > Key: JBDS-3486 > URL: https://issues.jboss.org/browse/JBDS-3486 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.CR1 > > > Max, in JBDS-3485, said: > {quote} > "I believe the tests all use BYOE install onto JavaEE, not JBDS installer. " that seems very unfortunate and weird since install grinder was written using JBDS to start with. > Can you please make sure we got tests that covers this so we can catch missing pieces like this faster in future ? Thanks. > {quote} > The install grinder tests [1] run two groovy scripts [2]. > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-gr... > [2] https://github.com/jbosstools/jbosstools-install-grinder/tree/master/scri... > One fetches and installs Eclipse; the other performs an installation from an update site or discovery site's directory.xml file. > In neither case is there support for installing JBDS (instead of Eclipse) and performing installations upon that base. > We should add support for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20100) how to make users aware of fuse and other tooling only being available from earlyaccess?

by Jim Tyrrell (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi... ] Jim Tyrrell commented on JBIDE-20100: ------------------------------------- Can we guarantee that products will always have products available on release of the current JBDS. I think with the structural split in the teams i.e. everyone is not on the same release cadence this can always be an issue. > how to make users aware of fuse and other tooling only being available from earlyaccess? > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20100 > URL: https://issues.jboss.org/browse/JBIDE-20100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > Attachments: JBIDE-20100-2.png > > > [~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features immediately on the install page. > Some comments: > "I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but where is the Fuse tooling in that list." > "<without earlyaccess> why doesn’t my screen shot tell me to use an older version of JBDS or something." > Suggestion: > "when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of choices, and something like (Select early Access) to enable this feature." > I'm fine exploring options to show early access features more prominently but would prefer we would not need to treat Fuse "special" so maybe we should have a "Early Access" section at the bottom instead of filtered in between everything else ? > and for any connectors that has additional/different features just add a "Extra features available in Early access " comment ? > But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is currently the state for devstudio 9) > [~crobson], [~aileenc] and [~lhein] got any suggestions ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-486) FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-486?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-486: ----------------------------- Attachment: fuse-new-licenses3.png fuse-new-licenses2.png fuse-new-licenses1.png Had to add these two sites to resolve deps when installing from the `fuseide/site/target/repository` site (to resolve Graphiti 0.13): * http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be... * http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.3.0.Be... Screenshots: [^fuse-new-licenses1.png] [^fuse-new-licenses2.png] [^fuse-new-licenses3.png] > FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > --------------------------------------------------------------------- > > Key: JBTIS-486 > URL: https://issues.jboss.org/browse/JBTIS-486 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: fuse-new-licenses1.png, fuse-new-licenses2.png, fuse-new-licenses3.png > > > Please make sure that Fuse Tooling is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

9 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2015