December 2016 - jbosstools-issues

[JBoss JIRA] (ERT-383) JSONEditor: NPE when working with an array of objects [EBZ#497261]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-383?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-383. --------------------------------- Resolution: Done > JSONEditor: NPE when working with an array of objects [EBZ#497261] > ------------------------------------------------------------------ > > Key: ERT-383 > URL: https://issues.jboss.org/browse/ERT-383 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: bzira, wst.json > Fix For: Neon.2 (4.6) > > > I have not been able to reproduce this consistently, but here it goes: > Create a JSON file with following content: > { > "thirdaddition": true, > "name": "JSONEditorTest2", > "secondaddition": 2, > "description": "JSONEditorTest description2", > "version": "1.0.1", > "main": "app.js", > "scripts": { > "start": "node app.js" > }, > "array_of_objects": [{"abc": 1234}, {"value": 1234 }]]}}}}}}]}], > "value": "test", > "anothervalue": "1234" > } > When adding and removing (invalid) closing brackets, then modifying the value of the second array element (value), I tend to see this exception: > java.lang.NullPointerException > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeAttrValue(JSONModelParser.java:89) > at org.eclipse.wst.json.core.internal.document.JSONModelParser.changeRegion(JSONModelParser.java:131) > at org.eclipse.wst.json.core.internal.document.JSONModelImpl.regionChanged(JSONModelImpl.java:654) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument._fireEvent(BasicStructuredDocument.java:542) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.fireStructuredDocumentEvent(BasicStructuredDocument.java:1180) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.internalReplaceText(BasicStructuredDocument.java:1964) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2423) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replaceText(BasicStructuredDocument.java:2408) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$2(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$3.run(JobSafeStructuredDocument.java:141) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replaceText(JobSafeStructuredDocument.java:144) > at org.eclipse.wst.sse.core.internal.text.BasicStructuredDocument.replace(BasicStructuredDocument.java:2368) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.access$0(JobSafeStructuredDocument.java:1) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument$1.run(JobSafeStructuredDocument.java:103) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.wst.sse.ui.EditorExecutionContext.execute(EditorExecutionContext.java:149) > at org.eclipse.wst.sse.core.internal.text.JobSafeStructuredDocument.replace(JobSafeStructuredDocument.java:106) > at org.eclipse.jface.text.projection.ProjectionTextStore.replace(ProjectionTextStore.java:103) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1094) > at org.eclipse.jface.text.AbstractDocument.replace(AbstractDocument.java:1119) > at org.eclipse.jface.text.projection.ProjectionDocument.replace(ProjectionDocument.java:625) > at org.eclipse.jface.text.DefaultDocumentAdapter.replaceTextRange(DefaultDocumentAdapter.java:233) > at org.eclipse.swt.custom.StyledText.modifyContent(StyledText.java:7374) > at org.eclipse.swt.custom.StyledText.sendKeyEvent(StyledText.java:8225) > at org.eclipse.swt.custom.StyledText.doBackspace(StyledText.java:2334) > at org.eclipse.swt.custom.StyledText.invokeAction(StyledText.java:7164) > at org.eclipse.swt.custom.StyledText.handleKey(StyledText.java:6022) > at org.eclipse.swt.custom.StyledText.handleKeyDown(StyledText.java:6049) > at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:5733) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4248) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1501) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1524) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1509) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1538) > at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1534) > at org.eclipse.swt.widgets.Canvas.sendKeyEvent(Canvas.java:515) > at org.eclipse.swt.widgets.Control.doCommandBySelector(Control.java:1090) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5817) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSResponder.interpretKeyEvents(NSResponder.java:68) > at org.eclipse.swt.widgets.Composite.keyDown(Composite.java:610) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5727) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227) > at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2140) > at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2402) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5789) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) > at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5218) > at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367) > at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) > at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695) > 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(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > 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) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4227: ---------------------------------- Maybe you can compare the two TP the Fuse one and the JBossTools one check the CDT dependencies because I remember we added some when Rob added a new terminal for better escape and color handling > JVM crash in development when launching the CDK server > ------------------------------------------------------ > > Key: JBDS-4227 > URL: https://issues.jboss.org/browse/JBDS-4227 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 10.2.0.GA > Reporter: Aurélien Pupier > Assignee: Rob Stryker > Attachments: hs_err_pid13472.log, hs_err_pid7936.log > > > When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing > {noformat} > Java frames: (J=compiled Java code, j=interpreted, Vv=VM code) > j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0 > j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39 > j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18 > j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489 > j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5 > j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4 > j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91 > j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87 > j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9 > j org.eclipse.core.internal.jobs.Worker.run()V+23 > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4231) OpenShift Explorer sometimes don't show the objects in Properties view

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4231?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-4231: ------------------------------------ Assignee: Jeff MAURY (was: Alexey Kazakov) > OpenShift Explorer sometimes don't show the objects in Properties view > ---------------------------------------------------------------------- > > Key: JBDS-4231 > URL: https://issues.jboss.org/browse/JBDS-4231 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: openshift > Affects Versions: 10.2.0.GA > Environment: * JBoss Developer Studio 10.2.0.GA > * CDK > Reporter: Ricardo Martinelli Oliveira > Assignee: Jeff MAURY > > After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4231) OpenShift Explorer sometimes don't show the objects in Properties view

by Ricardo Martinelli Oliveira (JIRA)

Ricardo Martinelli Oliveira created JBDS-4231: ------------------------------------------------- Summary: OpenShift Explorer sometimes don't show the objects in Properties view Key: JBDS-4231 URL: https://issues.jboss.org/browse/JBDS-4231 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: openshift Affects Versions: 10.2.0.GA Environment: * JBoss Developer Studio 10.2.0.GA * CDK Reporter: Ricardo Martinelli Oliveira Assignee: Alexey Kazakov After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23643) wrap process for moving a .Final target platform into /static/ folder w/ a Jenkins job

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23643?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23643: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > wrap process for moving a .Final target platform into /static/ folder w/ a Jenkins job > -------------------------------------------------------------------------------------- > > Key: JBIDE-23643 > URL: https://issues.jboss.org/browse/JBIDE-23643 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > When it's time to release the next set of .Final target platforms, the process ought to be run by a jenkins job rather than a local "copy this script into your console" operation. > See https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23652: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.3.AM2) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM1 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4204 at 12/21/16 1:21 PM: ------------------------------------------------------------ Proposed solution (for devstudio installer): https://github.com/jbdevstudio/jbdevstudio-product/pull/439 - please +1/-1. Proposed solution (for devstudio rpm): https://bugzilla.redhat.com/show_bug.cgi?id=1406886 was (Author: nickboldt): Proposed solution: https://github.com/jbdevstudio/jbdevstudio-product/pull/439 - please +1/-1. > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) JBoss IDE and dialogs not sizing correctly under Fedora 25

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4204: ---------------------------------- Proposed solution: https://github.com/jbdevstudio/jbdevstudio-product/pull/439 - please +1/-1. > JBoss IDE and dialogs not sizing correctly under Fedora 25 > ---------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Snjezana Peco > Labels: upstream > Fix For: 10.3.0.AM1 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 December 2016