[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23092:
-------------------------------
Description:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
* jbosstools-devdoc [no root pom]
* jbosstools-download.jboss.org [no root pom]
* jbosstools-maven-plugins no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci [no root pom]
* jbdevstudio-qa [no root pom]
* jbdevstudio-website [no root pom]
* jbdevstudio-artwork [no root pom]
was:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
* jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
* jbosstools-download.jboss.org [no root pom]
* jbosstools-devdoc [no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci [no root pom]
* jbdevstudio-qa [no root pom]
* jbdevstudio-website [no root pom]
* jbdevstudio-artwork [no root pom]
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-devdoc [no root pom]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-maven-plugins no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23092:
-------------------------------
Description:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
* jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
* jbosstools-download.jboss.org [no root pom]
* jbosstools-devdoc [no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci [no root pom]
* jbdevstudio-qa [no root pom]
* jbdevstudio-website [no root pom]
* jbdevstudio-artwork [no root pom]
was:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
* jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
* jbosstools-download.jboss.org [no root pom]
* jbosstools-devdoc [no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci
* jbdevstudio-qa
* jbdevstudio-website
* jbdevstudio-artwork
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> * jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
> Need to also branch these, but there's no root pom to adjust, so the script should just fail silently:
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-devdoc [no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci [no root pom]
> * jbdevstudio-qa [no root pom]
> * jbdevstudio-website [no root pom]
> * jbdevstudio-artwork [no root pom]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23092) add more projects to the list of projects to branch and/or update root pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23092?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23092:
-------------------------------
Description:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
* jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
* jbosstools-download.jboss.org [no root pom]
* jbosstools-devdoc [no root pom]
* jbosstools-versionwatch [no root pom]
* jbdevstudio-ci
* jbdevstudio-qa
* jbdevstudio-website
* jbdevstudio-artwork
was:
MIssing projects we could have included in the automated branching:
* jbosstools-integration-tests [root pom in ./]
* jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
* jbosstools-download.jboss.org [no root pom]
* jbosstools-devdoc [no root pom]
* jbosstools-versionwatch [no root pom]
> add more projects to the list of projects to branch and/or update root pom
> --------------------------------------------------------------------------
>
> Key: JBIDE-23092
> URL: https://issues.jboss.org/browse/JBIDE-23092
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> MIssing projects we could have included in the automated branching:
> * jbosstools-integration-tests [root pom in ./]
> * jbosstools-maven-plugins [root pom in ./tycho-plugins folder]
> * jbosstools-download.jboss.org [no root pom]
> * jbosstools-devdoc [no root pom]
> * jbosstools-versionwatch [no root pom]
> * jbdevstudio-ci
> * jbdevstudio-qa
> * jbdevstudio-website
> * jbdevstudio-artwork
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov resolved JBIDE-23068.
--------------------------------------
Assignee: Dmitrii Bocharov
Resolution: Done
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
> Assignee: Dmitrii Bocharov
> Attachments: magic_error_disapperance.webm
>
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23084) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Webservices]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23084?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23084.
----------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Webservices]
> ------------------------------------------------------------------------
>
> Key: JBIDE-23084
> URL: https://issues.jboss.org/browse/JBIDE-23084
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [Webservices]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 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)
9 years, 7 months
[JBoss JIRA] (JBIDE-23086) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Freemarker]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23086?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23086.
----------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Freemarker]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23086
> URL: https://issues.jboss.org/browse/JBIDE-23086
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [Freemarker]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 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)
9 years, 7 months
[JBoss JIRA] (JBIDE-23087) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23087?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23087.
----------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central]
> --------------------------------------------------------------------
>
> Key: JBIDE-23087
> URL: https://issues.jboss.org/browse/JBIDE-23087
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central, maven, project-examples
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [Central]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 Central 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)
9 years, 7 months
[JBoss JIRA] (JBIDE-23088) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [LiveReload]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23088?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23088.
----------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [LiveReload]
> -----------------------------------------------------------------------
>
> Key: JBIDE-23088
> URL: https://issues.jboss.org/browse/JBIDE-23088
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [LiveReload]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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 LiveReload 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)
9 years, 7 months
[JBoss JIRA] (JBIDE-23080) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23080?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-23080.
----------------------------------
Resolution: Done
> For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JavaEE]
> -------------------------------------------------------------------
>
> Key: JBIDE-23080
> URL: https://issues.jboss.org/browse/JBIDE-23080
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Friendly Jira Robot
> Priority: Blocker
> Labels: task
> Fix For: 4.4.1.Final
>
>
> For JBIDE 4.4.1.Final [JavaEE]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
> [Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Check out your existing *{color:orange}master{color}* branch:
> {code}
> git checkout master
> {code}
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Final-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.1.Final-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:orange}4.4.1.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.1.x{color}* branch:
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.4.1.x
> git push origin jbosstools-4.4.1.x
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
> {code}
> mvn clean verify -Dtpc.version=4.60.1.Final
> {code}
> 5. Close (do not resolve) this JIRA when done.
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] 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)
9 years, 7 months