March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13584) jbosstools-cleanup.sh script not counting build folders properly when regenerating composite site metadata

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13584?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13584. --------------------------------- Closing. > jbosstools-cleanup.sh script not counting build folders properly when regenerating composite site metadata > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13584 > URL: https://issues.jboss.org/browse/JBIDE-13584 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > Script is always returning 1 instead of an accurate count of the subfolders; therefore composite metadata is invalid. > eg., http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw... > (metadata says child, but 4 are listed) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12901) Show in File Browser shows error for EAP 5.1.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12901?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12901. --------------------------------- Already verified - closing again. > Show in File Browser shows error for EAP 5.1.2 > ---------------------------------------------- > > Key: JBIDE-12901 > URL: https://issues.jboss.org/browse/JBIDE-12901 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, UpStream > Affects Versions: 4.0.0.Beta1 > Environment: JBDS 6.0.0.Beta1 B45 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: upstream > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: ifile-error.png, RemoteSystemExplorer-JBIDE-12901.png > > > When you try to see what's in the deployment folder of a remote EAP 5.1.2 server, you will get an error (but the Remote System explorer will be opened correctly and will show the files). > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.ClassCastException: org.eclipse.core.internal.resources.Folder cannot be cast to org.eclipse.core.resources.IFile > at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getLocalResource(SystemViewRemoteFileAdapter.java:632) > at org.eclipse.rse.internal.files.ui.view.SystemViewRemoteFileAdapter.getImageDescriptor(SystemViewRemoteFileAdapter.java:574) > at org.eclipse.rse.ui.view.SystemTableViewProvider.getImage(SystemTableViewProvider.java:236) > at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:85) > at org.eclipse.rse.internal.ui.view.SystemDecoratingLabelProvider.getColumnImage(SystemDecoratingLabelProvider.java:46) > at org.eclipse.jface.viewers.TableColumnViewerLabelProvider.update(TableColumnViewerLabelProvider.java:71) > at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152) > at org.eclipse.jface.viewers.AbstractTableViewer.doUpdateItem(AbstractTableViewer.java:399) > at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) > at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167) > at org.eclipse.jface.viewers.AbstractTableViewer.createItem(AbstractTableViewer.java:277) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:757) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:649) > at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:636) > at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:592) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) > at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:590) > at org.eclipse.rse.ui.view.SystemTableView.inputChanged(SystemTableView.java:479) > at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:280) > at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1690) > at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1599) > at org.eclipse.rse.internal.ui.view.SystemTableViewPart.setInput(SystemTableViewPart.java:1578) > at org.jboss.ide.eclipse.as.rse.ui.SystemShowInTableAction.run(SystemShowInTableAction.java:77) > at org.jboss.ide.eclipse.as.rse.ui.RSEDeploymentPreferenceUI$2.openExplorer(RSEDeploymentPreferenceUI.java:115) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:89) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.runExplore(ExploreActionProvider.java:83) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider.access$0(ExploreActionProvider.java:82) > at org.jboss.tools.as.wst.server.ui.xpl.ExploreActionProvider$1.run(ExploreActionProvider.java:74) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4134) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3980) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3619) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:353) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584) > at org.eclipse.equinox.launcher.Main.run(Main.java:1438) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13263) Workspace metadata deployment does not work for AS 6

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13263?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13263. --------------------------------- Already verified - closing again. > Workspace metadata deployment does not work for AS 6 > ---------------------------------------------------- > > Key: JBIDE-13263 > URL: https://issues.jboss.org/browse/JBIDE-13263 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: JBoss AS 6.1.0 > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.0.1.Final > > > When you deploy a module to JBoss AS 6 and deployment is set to Workspace Metadata, the module doesn't get deployed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13572) Build target platform based on Juno SR2, Eclipse 4.2.2, Birt 4.2.2, WTP 3.4.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13572?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13572. --------------------------------- Closing. > Build target platform based on Juno SR2, Eclipse 4.2.2, Birt 4.2.2, WTP 3.4.2 > ----------------------------------------------------------------------------- > > Key: JBIDE-13572 > URL: https://issues.jboss.org/browse/JBIDE-13572 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, updatesite > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Need a Juno SR2 target platform. To be built here: https://github.com/jbosstools/jbosstools-target-platforms -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13816) Maven repository is not visible if its not active by default

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-13816: ---------------------------------------- Summary: Maven repository is not visible if its not active by default Key: JBIDE-13816 URL: https://issues.jboss.org/browse/JBIDE-13816 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.1.0.Alpha1 Reporter: Rastislav Wagner Assignee: Fred Bricon Fix For: 4.1.0.Alpha2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2256) Add chapter about how to configure JBoss AS startup parameters in eclipse

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-2256?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-2256. ------------------------------- The new content is visible at http://docs.jboss.org/tools/nightly/trunk/en/as/html_single/index.html#ed... although it will need a proper review later. Closing this issue. > Add chapter about how to configure JBoss AS startup parameters in eclipse > ------------------------------------------------------------------------- > > Key: JBDS-2256 > URL: https://issues.jboss.org/browse/JBDS-2256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Doc - JBossAS > Affects Versions: 5.0.0.GA > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 6.0.1.GA > > > There is no documentation about JBoss AS server startup parameters configuration (see forum reference for details) would be good to have it covered somewhere. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13010) Wrong versioning on modules N&N pages

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13010?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13010. --------------------------------- Everything is fixed except for version inconsistencies in ws modules - created JBIDE-13815. Closing this JIRA. > Wrong versioning on modules N&N pages > ------------------------------------- > > Key: JBIDE-13010 > URL: https://issues.jboss.org/browse/JBIDE-13010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.0.0.Beta2 > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.0.0.Beta2 > > > Some modules N&N pages have old versions in their title (in the <title> section of the HTML code) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13815) Wrong versioning on modules N&N pages - WS tools

by Martin Malina (JIRA)

Martin Malina created JBIDE-13815: ------------------------------------- Summary: Wrong versioning on modules N&N pages - WS tools Key: JBIDE-13815 URL: https://issues.jboss.org/browse/JBIDE-13815 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.1.0.Alpha1 Reporter: Martin Malina Assignee: Xavier Coulon Fix For: 4.1.0.Alpha2 Some modules N&N pages have different versions in their title/filename vs. web page hX. http://docs.jboss.org/tools/whatsnew/ws/ws-news-1.2.2.Beta1.html http://docs.jboss.org/tools/whatsnew/ws/ws-news-1.2.2.M5.html http://docs.jboss.org/tools/whatsnew/ws/ws-news-1.2.2.M1.html http://docs.jboss.org/tools/whatsnew/ws/ws-news-1.2.0.Beta1.html http://docs.jboss.org/tools/whatsnew/ws/ws-news-1.2.0.M2.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2500) synchronize deployed archive in EAP and JBDS project source files.

by Gary Hu (JIRA)

Gary Hu created JBDS-2500: ----------------------------- Summary: synchronize deployed archive in EAP and JBDS project source files. Key: JBDS-2500 URL: https://issues.jboss.org/browse/JBDS-2500 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Gary Hu Attachments: eclipse.png, ibm_rsa.png, jboss_try1.png, jboss_try2.png, Screenshot_Config.jpg Could JBDS provide a functionality that could synchronize the source and deployment in a two way manner. That is, if any change made at the server side after deploying could be pushed back to the source in the JBDS IDE. It seems that currently IBM RSA IDE has such feature with IBM WebSphere server. Please check the attached ibm_rsa.png for more details. Eclipse also could workaround this with Tomcat server by setting the "working directory" as the project workspace location something like ${workspace_loc:Project}. Please check the attached eclipse.png for more details. It doesn't seem that there's any additional functionality at server side that pushes the changes back to eclipse project. It's just a matter of setting eclipse working directory as the project source path. However, the JBDS doesn't seem to allow user to set the "Working directory" in this way. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13271) BrowserSim: simulator is closing unexpectedly while changing skin

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13271?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-13271: ------------------------------------------------ I download Alpha1-v20130306-0101-B124, on Windows everything is fine. Will test it on Fedora. > BrowserSim: simulator is closing unexpectedly while changing skin > ----------------------------------------------------------------- > > Key: JBIDE-13271 > URL: https://issues.jboss.org/browse/JBIDE-13271 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 4.0.0.CR1 > Environment: Windows 7 > Reporter: Yahor Radtsevich > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.1.0.Alpha2 > > > On some web pages BrowserSim is closing with the following stack trace while changing skin (see steps to reproduce): > {code} > Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed > at org.eclipse.swt.SWT.error(SWT.java:4361) > at org.eclipse.swt.SWT.error(SWT.java:4276) > at org.eclipse.swt.SWT.error(SWT.java:4247) > at org.eclipse.swt.widgets.Widget.error(Widget.java:468) > at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340) > at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725) > at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin. > progressChanged(AppleIPhone3ResizableSkin.java:247) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav > a:251) > at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR > equest(WebResourceLoadDelegate.java:225) > at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource > LoadDelegate.java:45) > at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java > :92) > at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method) > at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058) > at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822) > at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417) > at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152) > at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976) > at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method) > at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java: > 76) > at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064) > at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058) > at org.eclipse.swt.widgets.Widget.release(Widget.java:808) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873) > at org.eclipse.swt.widgets.Widget.release(Widget.java:811) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873) > at org.eclipse.swt.widgets.Widget.release(Widget.java:811) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873) > at org.eclipse.swt.widgets.Widget.release(Widget.java:811) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873) > at org.eclipse.swt.widgets.Widget.release(Widget.java:811) > at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873) > at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167) > at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java: > 790) > at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290) > at org.eclipse.swt.widgets.Widget.release(Widget.java:811) > at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446) > at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448) > at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse > rSim.java:673) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j > ava:433) > at java.util.Observable.notifyObservers(Unknown Source) > at java.util.Observable.notifyObservers(Unknown Source) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse > rSim.java:651) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java: > 248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758) > at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156 > ) > 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.swtjar.SWTLoader.main(SWTLoader.java:38) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 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 March 2013