October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21031) Version of AS features in 4.3.x branch is greater than in master (4.4.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21031?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21031: ------------------------------- Priority: Blocker (was: Major) > Version of AS features in 4.3.x branch is greater than in master (4.4.x) > ------------------------------------------------------------------------ > > Key: JBIDE-21031 > URL: https://issues.jboss.org/browse/JBIDE-21031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final, 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Versionwatch reports that in JBDS 9.0.1, these features are at version 3.3.1 (not 3.1.1): > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.x/as/... > But in 9.0.0 we had 3.1.0: > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.3.0.Fin... > So, in master, we have 3.2.0, which is seen by VW as being a lower version. > Solution: fix features in 4.3.x branch to use correct version of 3.1.1, or bump master to 3.4.0. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21027: ------------------------------------- I think it makes sense to move the early access prefs to the discovery plugin > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20976) Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20976: ------------------------------- Summary: Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) (was: Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)) > Create and use Neon M3 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21027) Central offers to install Early Access content when importing project examples (EA disabled)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21027?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21027: ---------------------------------------- The issue comes from the fact that the installation procedure isn't factorized between Central page and Example wizards. Example wizards use a procedure that is not aware of Early Access at all, leading to the issue reported here. The places in example that require a change are: * https://github.com/jbosstools/jbosstools-central/blob/master/central/plug... * https://github.com/jbosstools/jbosstools-central/blob/master/examples/plu... However, there is currently no easy substitution to that call. The InstallAction, in the SoftwarePage would be a good candidate but requires some changes to be consumed by the wizards. Or maybe most of this action should be moved to JBossDiscoveryUi (which is currently not aware of early access neither...) > Central offers to install Early Access content when importing project examples (EA disabled) > -------------------------------------------------------------------------------------------- > > Key: JBIDE-21027 > URL: https://issues.jboss.org/browse/JBIDE-21027 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, project-examples > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Mickael Istria > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > Attachments: angular.png > > > 1. Open Central with EA disabled > 2. Try to import kitchensink-angularjs project example > 3. AngularJS (EA version) is offered to install: > !angular.png! > 4. Press "Download & Install". > 5. AngularJS is installed without any warning that it's an EA content. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20976: ------------------------------------ These problems will have to remain until Neon.0.M3, available on November 13, 2015 [1]. I've reported them upstream here: * https://bugs.eclipse.org/bugs/show_bug.cgi?id=480913 (Web Tools) * https://bugs.eclipse.org/bugs/show_bug.cgi?id=476918 (Platform) [1] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedule > Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9) > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20976 > URL: https://issues.jboss.org/browse/JBIDE-20976 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: features_Mars.0-vs.1.vs.NeonM2.png.png, JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, plugins_Mars.0-vs.1.vs.NeonM2.png, versionwatch-features.png, versionwatch-plugins.png > > > Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS. > Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer). > Details in these logs: > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers... > Affected IUs (now sorted alphabetically): > {code} > org.eclipse.core.runtime 3.11.1.v20150903-1804 > org.eclipse.egit 4.0.2.201509141540-r > org.eclipse.egit.core 4.0.2.201509141540-r > org.eclipse.egit.doc 4.0.2.201509141540-r > org.eclipse.egit.ui 4.0.2.201509141540-r > org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 > org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 > org.eclipse.jdt 3.11.1.v20150904-0015 > org.eclipse.jdt.doc.user 3.11.1.v20150819-1130 > org.eclipse.jetty.webapp 9.2.13.v20150730 > org.eclipse.jetty.xml 9.2.13.v20150730 > org.eclipse.jgit 4.0.2.201509141540-r > org.eclipse.jgit.archive 4.0.2.201509141540-r > org.eclipse.jst.common.frameworks 1.1.701.v201509021802 > org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356 > org.eclipse.jst.web_core.feature 3.7.1.v201509021802 > org.eclipse.jst.web_ui.feature 3.7.1.v201509021802 > org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443 > org.eclipse.pde 3.11.1.v20150904-0345 > org.eclipse.pde.doc.user 3.11.1.v20150903-1352 > org.eclipse.platform 4.5.1.v20150904-0015 > org.eclipse.platform.doc.user 4.5.1.v20150819-1130 > org.eclipse.rcp 4.5.1.v20150904-0015 > org.eclipse.sapphire 9.0.1.201509151939 > org.eclipse.sapphire.java 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt 9.0.1.201509151939 > org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939 > org.eclipse.sapphire.modeling 9.0.1.201509151939 > org.eclipse.sapphire.modeling.xml 9.0.1.201509151939 > org.eclipse.sapphire.osgi 9.0.1.201509151939 > org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939 > org.eclipse.sapphire.platform 9.0.1.201509151939 > org.eclipse.sapphire.ui 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939 > org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939 > org.eclipse.sapphire.workspace 9.0.1.201509151939 > org.eclipse.sapphire.workspace.ui 9.0.1.201509151939 > org.eclipse.swt 3.104.1.v20150825-0743 > org.eclipse.wst.common_core.feature 3.7.1.v201508262220 > org.eclipse.wst.common_ui.feature 3.7.1.v201508262220 > org.eclipse.wst.jsdt.feature 1.6.201.v201508262249 > org.eclipse.wst.server.core 1.7.0.v201508271522 > org.eclipse.wst.server.discovery 1.1.0.v201508271522 > org.eclipse.wst.server.ui 1.5.201.v201509022125 > org.eclipse.wst.server_core.feature 3.3.600.v201508271522 > org.eclipse.wst.server_ui.feature 3.3.600.v201509022125 > org.eclipse.wst.validation 1.2.700.v201508251749 > org.eclipse.wst.web_core.feature 3.7.1.v201508271605 > org.eclipse.wst.web_ui.feature 3.7.1.v201509022125 > org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926 > org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605 > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21022: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.4.0.Alpha1 > > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21022) open of .md files in project examples don't use markdown editor

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21022?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-21022: ----------------------------------- Assignee: Snjezana Peco (was: Fred Bricon) > open of .md files in project examples don't use markdown editor > --------------------------------------------------------------- > > Key: JBIDE-21022 > URL: https://issues.jboss.org/browse/JBIDE-21022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.4.0.Alpha1 > > > even though we have JBDS-3259 readme.md opened by project-examples still seem to use the default editor as opposed to the wiki text editor. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3554: ----------------------------- Attachment: p2diff.log.txt > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3554) Integrate/Enable CodeRecommenders substring completion in JBDS 10

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3554?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3554: ----------------------------- Description: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* [^p2diff.log.txt] was: Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. *Project page/sources:* https://www.eclipse.org/recommenders/manual/ *Version:* 2.2.4 (part of Mars) *License and owner:* EPL, Eclipse Community/CodeTrails *Original p2 repo:* included in Mars repository *JBoss mirror:* will use our Mars mirror *Include Sources:* No *Affected JBoss Tools components:* JBDS feature and product *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) *Type of dependency:* distribution *List of bundles added/removed:* {code} TODO {code} > Integrate/Enable CodeRecommenders substring completion in JBDS 10 > ----------------------------------------------------------------- > > Key: JBDS-3554 > URL: https://issues.jboss.org/browse/JBDS-3554 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: p2-product, target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 10.0.0.Alpha1 > > Attachments: p2diff.log.txt > > > Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/ > JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default. > *Project page/sources:* https://www.eclipse.org/recommenders/manual/ > *Version:* 2.2.4 (part of Mars) > *License and owner:* EPL, Eclipse Community/CodeTrails > *Original p2 repo:* included in Mars repository > *JBoss mirror:* will use our Mars mirror > *Include Sources:* No > *Affected JBoss Tools components:* JBDS feature and product > *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse) > *Type of dependency:* distribution > *List of bundles added/removed:* > [^p2diff.log.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- A few comments: the created server adapter says "CDK Server Adapter", I think it should just say "Red Hat CDK". There is a vagrant icon - I would leave that out of this server adapter for now. Its not generic vagrant. Similar some of the pages in the wizard says Vagrant server adapter - it should say CDK in this case. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 6 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 October 2015