[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 updated JBIDE-20804:
--------------------------------
Fix Version/s: 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
> 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.Predicate, no source can be found
> The problem is caused by the class file being found in the wildfly-cli 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
[JBoss JIRA] (JBIDE-20792) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Freemarker]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20792?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-20792.
---------------------------------
Resolution: Done
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Freemarker]
> --------------------------------------------------------------
>
> Key: JBIDE-20792
> URL: https://issues.jboss.org/browse/JBIDE-20792
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Freemarker]: 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 Freemarker 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
[JBoss JIRA] (JBIDE-20783) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [OpenShift]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20783?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-20783.
----------------------------------
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [OpenShift]
> -------------------------------------------------------------
>
> Key: JBIDE-20783
> URL: https://issues.jboss.org/browse/JBIDE-20783
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [OpenShift]: 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 OpenShift 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
[JBoss JIRA] (JBIDE-20782) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20782?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-20782.
----------------------------------
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Base]
> --------------------------------------------------------
>
> Key: JBIDE-20782
> URL: https://issues.jboss.org/browse/JBIDE-20782
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Base]: 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 Base 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
[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debuggingapps deployed on Wildfly
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-20804:
-----------------------------------
Summary: Flaky source lookup while debuggingapps 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
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.Predicate, no source can be found
The problem is caused by the class file being found in the wildfly-cli 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
[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 reassigned JBIDE-20804:
-----------------------------------
Assignee: Fred Bricon
> 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
>
> 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.Predicate, no source can be found
> The problem is caused by the class file being found in the wildfly-cli 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
[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 updated JBIDE-20804:
--------------------------------
Summary: Flaky source lookup while debugging apps deployed on Wildfly (was: Flaky source lookup while debuggingapps deployed on Wildfly)
> 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
>
> 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.Predicate, no source can be found
> The problem is caused by the class file being found in the wildfly-cli 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
[JBoss JIRA] (JBIDE-20775) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Aerogear]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20775?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20775:
--------------------------------------
Assignee: Ilya Buziuk
> 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: Ilya Buziuk
> 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
[JBoss JIRA] (JBIDE-20776) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central Discovery]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20776?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20776:
--------------------------------------
Assignee: Mickael Istria
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Central Discovery]
> ---------------------------------------------------------------------
>
> Key: JBIDE-20776
> URL: https://issues.jboss.org/browse/JBIDE-20776
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Central Discovery]: 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 Central Discovery 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
[JBoss JIRA] (JBIDE-20790) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Webservices]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20790?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-20790:
--------------------------------------
Assignee: Xavier Coulon
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Webservices]
> ---------------------------------------------------------------
>
> Key: JBIDE-20790
> URL: https://issues.jboss.org/browse/JBIDE-20790
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [Webservices]: 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 Webservices 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