[JBoss JIRA] (JBIDE-20385) Upgrade FreeMarker to 2.3.23
by Daniel Dekany (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20385?page=com.atlassian.jira.plugi... ]
Daniel Dekany commented on JBIDE-20385:
---------------------------------------
Note that this change is just increasing the `freemarker.org:freemarker` dependency version, and it would make the plugin significantly more useful.
> Upgrade FreeMarker to 2.3.23
> ----------------------------
>
> Key: JBIDE-20385
> URL: https://issues.jboss.org/browse/JBIDE-20385
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.3.x
>
>
> 2.3.23 has added new listing-related directives and "built-ins". Also it has support for camel case (like `?startsWith` instead of `?starts_with`).
--
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:
--------------------------------
Description:
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
was:
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 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
> 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
[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20804:
---------------------------------------------
one note, if it keeps looking until found source match it shuold still cache the last found to not keep looking on every attempt to look it up in a session.
> 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 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:
--------------------------------
Description:
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 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
was:
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
> 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 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-20810) For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20810?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-20810 at 9/24/15 3:18 PM:
-------------------------------------------------------------
Bumped:
build, build-sites
Nothing to do:
dl.jb.org, devdoc, versionwatch
Not yet bumped:
maven-plugins (cc: [~mickael_istria] )
was (Author: nickboldt):
Bumped:
build, build-sites
Nothing to do:
dl.jb.org, devdoc
Not yet bumped:
maven-plugins, versionwatch (cc: [~mickael_istria] )
> For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20810
> URL: https://issues.jboss.org/browse/JBIDE-20810
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Final
>
>
> For JBIDE 4.3.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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-20779) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20779?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20779:
----------------------------------------
Maven plugins were released as 0.23.1 before we built CR1, and master is already ready for next development, it's version being 0.23.2-SNAPSHOT.
> For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20779
> URL: https://issues.jboss.org/browse/JBIDE-20779
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.4.0.Alpha1
>
>
> For JBIDE 4.4.0.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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-20810) For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20810?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20810:
------------------------------------
Bumped:
build, build-sites
Nothing to do:
dl.jb.org, devdoc
Not yet bumped:
maven-plugins, versionwatch (cc: [~mickael_istria] )
> For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20810
> URL: https://issues.jboss.org/browse/JBIDE-20810
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Final
>
>
> For JBIDE 4.3.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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