June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18409) Server Adapter: Allow to show application in external device/browser

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18409?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18409: ------------------------------------- Summary: Server Adapter: Allow to show application in external device/browser (was: Server Adapter: Add choice to show application in external device/browser) > Server Adapter: Allow to show application in external device/browser > -------------------------------------------------------------------- > > Key: JBIDE-18409 > URL: https://issues.jboss.org/browse/JBIDE-18409 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Joao Viragine > Labels: openshift_v2, openshift_v3, server_adapter > Fix For: 4.4.x > > > It would be nice if we had the option: Show In/Web Browser on External Device for OpenShift Server as we have for JBoss EAP Server. (Servers/(Application)/Show In/Add Web Browser on External Device) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21801) Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21801: -------------------------------- Story Points: 25 > Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup > ----------------------------------------------------------------------------- > > Key: JBIDE-21801 > URL: https://issues.jboss.org/browse/JBIDE-21801 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.3.1.Beta2 > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Fix For: 4.4.x > > Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png > > > first technical investigation: > - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%... > and it returns: > {noformat} > <?xml version="1.0" encoding="UTF-8"?> > <result> > <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText> > <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText> > <customParams> > <param name="company" label="Company" /> > <param name="country" label="Country" > > <options multiple="false"> > </options> > </param> > <param name="downloadURL" label="Downloaded file" > > <options multiple="false"> > <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/> > </options> > </param> > </customParams> > </result> > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20686: --------------------------------------- I don't recall how it was behaving back there, it was in 9/2015 and why I was arguing like this. At the moment, when I look at it, I agree with you. I guess something was not working pretty well with autodetection of oc binary on path or I was not aware of that feature yet at that time. Now I would consider this as rejected. > Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20686 > URL: https://issues.jboss.org/browse/JBIDE-20686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, preferences > Fix For: 4.4.x > > > In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22562: ---------------------------------------- Since last release, jbosstools-playground is not used any more by JBoss Tools. What's the best procedure? Should I close this Jira and ask for having the component marked as archived? > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Playground]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-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 Playground 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22075) Confusing error message when trying to attach remote debugger to OS app run in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22075?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22075: ------------------------------------- Labels: debugging openshift_v3 (was: openshift_v3) > Confusing error message when trying to attach remote debugger to OS app run in debug mode > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22075 > URL: https://issues.jboss.org/browse/JBIDE-22075 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: debugging, openshift_v3 > Fix For: 4.4.x > > Attachments: error-in-launching-remote-debugger.png, error-launching-remote-debugger.png, remote-debugger-already-launched.png > > > If you restart the server adapter in debug mode ("Restart in Debug" in the context menu to your server adapter) the remote debugger is launched automatically. > If you're not aware of this and try to launch the remote debugger entry (that was created automatically), you will face an error telling you that it cannot connect (since there's already an instance sitting on the ports). It's not obvious to the dummy user, we should improve this error-message > When I am trying to run remote debugging of an application on OpenShift I get following error > !!error-in-launching-remote-debugger.png! ! > {code} > Failed to connect to remote VM > com.sun.jdi.connect.spi.ClosedConnectionException > at org.eclipse.jdi.internal.connect.SocketTransportService.readHandshake(SocketTransportService.java:222) > at org.eclipse.jdi.internal.connect.SocketTransportService.access$7(SocketTransportService.java:214) > at org.eclipse.jdi.internal.connect.SocketTransportService$3.run(SocketTransportService.java:185) > at java.lang.Thread.run(Thread.java:745) > {code} > *Steps to reproduce:* > ASSERT: Have an OpenShift 3 application based on eap 6 template with server adapter and project in workspace. > EXEC: Select "Restart in Debug" in context menu of server adapter. > ASSERT: Server adapter is in state debugging ("[Debugging, Started]"). > EXEC: Click on Debug Remote debugger to 'server adapter name' workbench tool item to start debugging. > RESULT: Error is shown. > EXPECTED RESULT: The error message should tell you that there already is an instance running. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22562: -------------------------------------- Assignee: Mickael Istria > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Playground]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-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 Playground 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22562) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22562?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22562: ----------------------------------- Story Points: 1 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [Playground] > ------------------------------------------------------------- > > Key: JBIDE-22562 > URL: https://issues.jboss.org/browse/JBIDE-22562 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [Playground]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-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 Playground 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-22557: -------------------------------------- Assignee: Nick Boldt > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-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)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22591) Saving new username/pw during prompt for pw while starting cdk fails

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22591?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22591: -------------------------------- Fix Build: ER6 Story Points: 3 > Saving new username/pw during prompt for pw while starting cdk fails > --------------------------------------------------------------------- > > Key: JBIDE-22591 > URL: https://issues.jboss.org/browse/JBIDE-22591 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.Alpha1 > > > When the server is in a project rather than in memory, persisting changes to the server (ie changing its username) will fail because the scheduling rule for starting the server does not include the ability to modify projects. This scenario will need to be identified (is server in memory or project) and a workspace job will need to be scheduled to properly persist the changes. > java.lang.IllegalArgumentException: Attempted to beginRule: L/Servers/Container Development Environment.server, does not match outer scope rule: Container Development Environment > at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) > at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:134) > at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:333) > at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:85) > at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:307) > at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:121) > at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:2188) > at org.eclipse.core.internal.resources.File.setContents(File.java:334) > at org.eclipse.core.internal.resources.File.setContents(File.java:434) > at org.eclipse.wst.server.core.internal.Base.saveToFile(Base.java:251) > at org.eclipse.wst.server.core.internal.Server.saveToFile(Server.java:471) > at org.eclipse.wst.server.core.internal.Base.doSave(Base.java:264) > at org.eclipse.wst.server.core.internal.Server.doSave(Server.java:466) > at org.eclipse.wst.server.core.internal.ServerWorkingCopy.save(ServerWorkingCopy.java:434) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.CDKServer.getPassword(CDKServer.java:124) > at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(CDKLaunchController.java:158) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22557) For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22557?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22557: ----------------------------------- Story Points: 1 > For JBIDE 4.4.1.Alpha1: Prepare for 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22557 > URL: https://issues.jboss.org/browse/JBIDE-22557 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.1.Alpha1 > > > For JBIDE 4.4.1.Alpha1 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 1. Check out your existing *{color:orange}master{color}* branch: > {code} > git checkout master > {code} > 2. Update your *{color:orange}master{color}* root pom to use the latest parent pom version, *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.1.Alpha1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:orange}4.4.1.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.25.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 4. Ensure you've *built & run tests* using the latest target platform version 4.60.0.Final-SNAPSHOT (4.60 = Eclipse Neon.0) > {code} > mvn clean verify -Dtpc.version=4.60.0.Final-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)

9 years, 9 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 June 2016