September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20775) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20775?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-20775. -------------------------------- Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear] > ------------------------------------------------------------ > > Key: JBIDE-20775 > URL: https://issues.jboss.org/browse/JBIDE-20775 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Aerogear]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20803: --------------------------------------------- another example: {code}jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://download.jboss.org/jbosstools/discovery/stable/integration-stack/{code} this one is much more appropriate, the stable release for 4.2.4 is stated to point to the *stable* integration stack url. But there are a few problems: a) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? b) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should *never* composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. Ill open a jira for these issues since this is definitely not right. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20817) For JBIDE 4.3.0.Final: Code Freeze + Branch [JST]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20817?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20817. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [JST] > ------------------------------------------------- > > Key: JBIDE-20817 > URL: https://issues.jboss.org/browse/JBIDE-20817 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [JST]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20816) For JBIDE 4.3.0.Final: Code Freeze + Branch [JavaEE]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20816?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20816. ---------------------------------- Assignee: Alexey Kazakov Resolution: Done > For JBIDE 4.3.0.Final: Code Freeze + Branch [JavaEE] > ---------------------------------------------------- > > Key: JBIDE-20816 > URL: https://issues.jboss.org/browse/JBIDE-20816 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions, jsf, seam2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [JavaEE]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20804: ---------------------------------------- Fred is positive that the fix is 100% safe. Let's fix it for CR2. > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20804: ----------------------------------- Fix Version/s: 4.3.0.CR2 (was: 4.4.0.Alpha1) > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20804: ----------------------------------- Priority: Critical (was: Major) > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20803: --------------------------------------------- example: {code}jboss.discovery.site.integration-stack.url|devstudio|9.0.0.GA=https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.central_master/latest/all/repo/{code} this should raise red lights to anyone reviewing it since: a) it is mixing a *stable* release with *snapshots* b) that long/huge url "https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce..." is a complete internal detail, should never end up in users p2 list > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20803) script process for merging IS jars into JBT/JBDS discovery sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20803?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20803: --------------------------------------------- I dont follow why you make it look like the discovery site is and updatesite url. It will never be the right thing to do as we have it setup now. When I wrote "point it where it should be pointing at release. On our main updatesite." I meant it. the url IS should get its bits from when released into developpment is http://download.jboss.org/jbosstools/mars/development/updates/ and when we go final it is http://download.jboss.org/jbosstools/mars/stable/updates/ It should *never* be a site from snapshots, nor should our stable have links to development, nor should our development have links to nighlty. Please remember that the site linked from the discovery site plugin.xml gets *added* to users p2 update manager thus we should *not* have a setup that result in crossed streams. So please don't do this. do it right and have the updatesite url central will add point to a matching site, i.e. http://download.jboss.org/jbosstools/mars/stable/updates/ Then the *only* time you need to change anything in ide.properties are in case of before IS are part of the release and the nightly builds will point to something else. > script process for merging IS jars into JBT/JBDS discovery sites > ---------------------------------------------------------------- > > Key: JBIDE-20803 > URL: https://issues.jboss.org/browse/JBIDE-20803 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, discovery, integration-platform > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Need to document and script how to get the IS jars into the JBT/JBDS discovery sites. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20804: ------------------------------------- I investigated because [~maxandersen] couldn't get sources for EAP 6.4. Couldn't reproduce his issue, but found that particular one in WildFly. The wildfly-cli client jar shades a number of 3rd party libraries (undertow, fusesource stuff, picketbox, other jboss and wildfly classes). So that represents a significant number of classes that would fail to get their source attached should you try to debug the Wildfly stack. > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2015