August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23011) Docker Explorer broken on Windows

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23011?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23011: ------------------------------------ The way the devstudio core feature [1] works: * it INCLUDES some features/plugins, which are version-locked to the product or core feature (BYOE) version. These INCLUDES can only be updated when a new version of devstudio is released onto devstudio.redhat.com. * it REQUIRES other features/plugins, which are NOT version-locked and can be updated at any time from any other 3rd party site, like http://download.eclipse.org/linuxtools/updates-docker-nightly/ [1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... Since the Docker plugins [2] are REQUIRED, but not INCLUDED, we can update them independent of a devstudio release. [2] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... But yes, there will be no formal release of 10.1.0.AM3 -- just the staging site. https://devstudio.redhat.com/10.0/staging/updates/ > Docker Explorer broken on Windows > --------------------------------- > > Key: JBIDE-23011 > URL: https://issues.jboss.org/browse/JBIDE-23011 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker > Affects Versions: 4.4.1.AM3 > Reporter: Martin Malina > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.4.1.Final > > Attachments: docker-explorer.jpg, jbide23011.png, jbide23011_2.png > > > [reply] [−] Description Martin Malina CLA Friend 2016-08-16 08:51:31 EDT > Created attachment 263612 [details] > Broken Docker Explorer view > I just installed a brand new installation of Red Hat JBoss Developer Studio 10.1.0.AM3 which contains Docker Tooling 2.1.0.201608101805 on Windows and when I open Docker Explorer, it contains a red X and "Failed to create the part's controls". Also, there is a button that says Details > >. > There is this NPE in the error log view: > {code} > java.lang.NullPointerException > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.reloadConnections(DockerConnectionManager.java:63) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.<init>(DockerConnectionManager.java:50) > at org.eclipse.linuxtools.docker.core.DockerConnectionManager.getInstance(DockerConnectionManager.java:44) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.getInitialInput(DockerExplorerView.java:93) > at org.eclipse.ui.navigator.CommonNavigator.createPartControl(CommonNavigator.java:206) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createConnectionsPane(DockerExplorerView.java:195) > at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerView.createPartControl(DockerExplorerView.java:147) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityView.createPartControl(CompatibilityView.java:143) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:341) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966) > at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:931) > at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151) > at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375) > at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74) > at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$1.run(PartRenderingEngine.java:536) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:520) > at org.eclipse.e4.ui.workbench.renderers.swt.ElementReferenceRenderer.createWidget(ElementReferenceRenderer.java:70) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:975) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:651) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1317) > at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:72) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:4813) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:94) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:617) > at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:581) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:770) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:744) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:682) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:677) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1205) > at org.eclipse.ui.internal.WorkbenchPage.showPart(WorkbenchPage.java:1283) > at org.eclipse.ui.internal.WorkbenchPage.busyShowView(WorkbenchPage.java:1274) > at org.eclipse.ui.internal.WorkbenchPage$12.run(WorkbenchPage.java:4316) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4312) > at org.eclipse.ui.internal.WorkbenchPage.showView(WorkbenchPage.java:4292) > at org.eclipse.ui.internal.quickaccess.ViewElement.execute(ViewElement.java:77) > at org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:200) > at org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:507) > at org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:497) > at org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:542) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:168) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4410) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1079) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1103) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1088) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1130) > at org.eclipse.swt.widgets.Text.sendKeyEvent(Text.java:1789) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1126) > at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1547) > at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4910) > at org.eclipse.swt.widgets.Text.WM_CHAR(Text.java:2722) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:4791) > at org.eclipse.swt.widgets.Text.windowProc(Text.java:2704) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5102) > at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method) > at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2552) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3814) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} > This is a tracking issue for this upstream BZ: https://bugs.eclipse.org/bugs/show_bug.cgi?id=499745 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-22446. -------------------------------- Resolution: Done Resolving. [~mmalina] or [~jeffmaury] please reopen if there's still something we need to do here to achieve Total Happiness. :D > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22446) Release process should disallow inclusion of snapshots artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22446?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22446: ------------------------------------ Bug fixed: First, we pass $\{BUILD_ALIAS} into the rule config: https://github.com/jbosstools/jbosstools-build/commit/8536633b92966b7cd4e... Then, we only read the property value if it's not already defined via the config (==null): https://github.com/jbosstools/jbosstools-maven-plugins/commit/80ff81a32ac... Now, you can pass rebuild the parent pom (or another other project) using -DBUILD_ALIAS=AM3 or AM2 or Final or whatever to see different enforcement results in the build. > Release process should disallow inclusion of snapshots artifacts > ---------------------------------------------------------------- > > Key: JBIDE-22446 > URL: https://issues.jboss.org/browse/JBIDE-22446 > Project: Tools (JBoss Tools) > Issue Type: Release > Components: build > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > 4.4.0.Alpha2 was generated with a SNAPSHOT dependency. This should be avoided in future releases even for Alpha ones > Update: This issues is for adding some automated test/check to detect situation when our release includes a snapshot dependency. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-23019: --------------------------------------- For more info about OpenShift 3 tests execution and existing issues see reference https://docs.google.com/document/d/1CBzAuNu5hQ3VxU7Nk9V_p91pn2zpG0hmMIyos... > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23019) Integration tests: have them running automatically, continuously

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23019?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23019: ------------------------------------------ We already have smoke tests for PRs but the job is currently disabled: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/All/job... > Integration tests: have them running automatically, continuously > ---------------------------------------------------------------- > > Key: JBIDE-23019 > URL: https://issues.jboss.org/browse/JBIDE-23019 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > > The integration tests suite is very lenghty to run and should thus be run in a continuous manner on our CI. > There are several pain-points currently: > - there's no dedicated OS instance to run them against > - tests are not stable > - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23020) integration tests: Have a dedicated OS instance

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23020: ---------------------------------------- Summary: integration tests: Have a dedicated OS instance Key: JBIDE-23020 URL: https://issues.jboss.org/browse/JBIDE-23020 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: openshift Affects Versions: 4.4.1.AM3 Reporter: Andre Dietisheim We dont have a dedicated OS instance for the integration tests. Currently the best approach is to have a local CDK since console.engint.openshift.com takes about 2x the time to execute these. Automatically installing the CDK in jenkins isnt possible since nested virtualization isnt possible: https://engineering.redhat.com/rt/Ticket/Display.html?id=410151 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBTIS-838. ---------------------------- Resolution: Done reopened to set component = fuse, so jiralint won't complain. > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 8.0.0.GA, 9.0.0.GA > Reporter: Abel BOUCHAMA > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-838: ----------------------------- Component/s: Fuse IDE > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 8.0.0.GA, 9.0.0.GA > Reporter: Abel BOUCHAMA > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBTIS-838. ---------------------------- Fix Version/s: 9.0.0.GA Resolution: Duplicate Issue Closing as DUPE of FUSETOOLS-2041. > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 8.0.0.GA, 9.0.0.GA > Reporter: Abel BOUCHAMA > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-838) Unable to add nested <when> in Camel - Blueprint

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-838?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBTIS-838: -------------------------------- Assignee: Paul Leacu > Unable to add nested <when> in Camel - Blueprint > ------------------------------------------------ > > Key: JBTIS-838 > URL: https://issues.jboss.org/browse/JBTIS-838 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 8.0.0.GA, 9.0.0.GA > Reporter: Abel BOUCHAMA > Assignee: Paul Leacu > Fix For: 9.0.0.GA > > > When we add <when> condition in existing <when> block in blueprint.xml source view, and we save it. If we go after to design view and come back after to source view, the new block <when> disappear. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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