August 2008 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-2556) Problems occurred when invoking code from plug-in: "org.jboss.tools.common.model". is occured if save pages.xml with empty tag <exception></exception>

by Anton Klimkovich (JIRA)

Problems occurred when invoking code from plug-in: "org.jboss.tools.common.model". is occured if save pages.xml with empty tag <exception></exception> ------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-2556 URL: https://jira.jboss.org/jira/browse/JBIDE-2556 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.0.0.alpha Environment: 200807212151-nightly Reporter: Anton Klimkovich Assignee: Alexey Kazakov Attachments: exception.txt EXECUTE: Create Seam web project EXECUTE: Open pages.xml on source tab. EXECUTE: Call CA and select <exception> ASSERT: <exception></exception> shoud be inserted EXECUTE: Save pages.xml FAILURE: Problems occurred when invoking code from plug-in: "org.jboss.tools.common.model". Log attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2531) For html tags in properties view for style attribute is not present the button of a call css dialog

by Dzmitry Sakovich (JIRA)

For html tags in properties view for style attribute is not present the button of a call css dialog --------------------------------------------------------------------------------------------------- Key: JBIDE-2531 URL: https://jira.jboss.org/jira/browse/JBIDE-2531 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 2.1.0.GA Reporter: Dzmitry Sakovich Assignee: Dzmitry Sakovich Fix For: 3.0.0.alpha Attachments: Screenshot-1.png, Screenshot-2.png This bug is related to feature request https://jira.jboss.org/jira/browse/JBIDE-2499 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-2645) Lot of NPE's in seam pages.xml editor

by Max Rydahl Andersen (JIRA)

Lot of NPE's in seam pages.xml editor ------------------------------------- Key: JBIDE-2645 URL: https://jira.jboss.org/jira/browse/JBIDE-2645 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.alpha Reporter: Max Rydahl Andersen Assignee: Daniel Azarov Fix For: 3.0.0.beta1 I'm seeing alot of these in the error log when I have seam pages.xml editor open: Caused by: java.lang.NullPointerException at org.jboss.tools.seam.ui.pages.editor.figures.PageFigure$GroupBorder.paint(PageFigure.java:236) at org.eclipse.draw2d.Figure.paintBorder(Figure.java:1066) at org.eclipse.draw2d.Figure.paint(Figure.java:1052) at org.eclipse.draw2d.Figure.paintChildren(Figure.java:1087) at org.eclipse.draw2d.Figure.paintClientArea(Figure.java:1119) at org.eclipse.draw2d.Figure.paint(Figure.java:1051) at org.eclipse.draw2d.Figure.paintChildren(Figure.java:1087) at org.eclipse.draw2d.Figure.paintClientArea(Figure.java:1119) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-2682) New console configuration wizard propose project name as console configuration name even if such configuration exists

by Dima Geraskov (JIRA)

New console configuration wizard propose project name as console configuration name even if such configuration exists --------------------------------------------------------------------------------------------------------------------- Key: JBIDE-2682 URL: https://jira.jboss.org/jira/browse/JBIDE-2682 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.0.0.alpha Reporter: Dima Geraskov Assignee: Dima Geraskov Fix For: 3.0.0.beta1 Need to provide Project_name (1), Project_name (2) and so on. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-2684) Component <rich:insert> doesn't work in VPE. Exception appears.

by Dzmitry Sakovich (JIRA)

Component <rich:insert> doesn't work in VPE. Exception appears. --------------------------------------------------------------- Key: JBIDE-2684 URL: https://jira.jboss.org/jira/browse/JBIDE-2684 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.alpha Reporter: Dzmitry Sakovich Assignee: Dzmitry Sakovich EXECUTE: Import richfaces-demo-3.1.3.GA.war in workspace EXECUTE: Open /WebContent/richfaces/dataTable.xhtml EXCEPTION Appears: java.lang.NullPointerException at org.jboss.tools.jsf.vpe.richfaces.template.RichFacesInsertTemplate.create(RichFacesInsertTemplate.java:112) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:436) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:601) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:517) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:513) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:255) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:576) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.buildDom(VpeVisualDomBuilder.java:217) at org.jboss.tools.vpe.editor.VpeController.init(VpeController.java:284) at org.jboss.tools.vpe.editor.VpeEditorPart$16.load(VpeEditorPart.java:748) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.onLoadWindow(MozillaEditor.java:510) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.access$2(MozillaEditor.java:505) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor$4.onLoadWindow(MozillaEditor.java:240) at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.onStateChange(XulRunnerBrowser.java:403) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1541) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3031) at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.createPartControl(MozillaEditor.java:288) at org.jboss.tools.vpe.editor.VpeEditorPart.createVisualEditor(VpeEditorPart.java:754) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.pageChange(JSPMultiPageEditor.java:223) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:421) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:125) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:661) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:428) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:594) at org.eclipse.ui.internal.EditorReference.getEditor(EditorReference.java:266) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditorBatched(WorkbenchPage.java:2820) at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:2729) at org.eclipse.ui.internal.WorkbenchPage.access$11(WorkbenchPage.java:2721) at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:2673) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2668) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2652) at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:2643) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:646) at org.eclipse.ui.ide.IDE.openEditor(IDE.java:605) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:318) at org.eclipse.jdt.internal.ui.javaeditor.EditorUtility.openInEditor(EditorUtility.java:160) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:228) at org.eclipse.jdt.ui.actions.OpenAction.run(OpenAction.java:207) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.dispatchRun(SelectionDispatchAction.java:274) at org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(SelectionDispatchAction.java:250) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerActionGroup.handleOpen(PackageExplorerActionGroup.java:363) at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart$5.open(PackageExplorerPart.java:603) at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:820) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:880) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:48) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:818) at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1079) at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1183) at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:263) at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:257) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:297) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:585) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-1080) Field Destination is not editable by hand in Project archives-> New WAR Wizard.

by Anton Klimkovich (JIRA)

Field Destination is not editable by hand in Project archives-> New WAR Wizard. ------------------------------------------------------------------------------- Key: JBIDE-1080 URL: http://jira.jboss.com/jira/browse/JBIDE-1080 Project: JBoss Tools Issue Type: Bug Affects Versions: 2.0.0.Beta4 Reporter: Anton Klimkovich Priority: Minor Attachments: not editable.PNG Create any project Open Project archives View Move project to war In New WAR Wizard field Field Destination is not editable by hand. Look at Screenshot. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

5
16
0 / 0

[JBoss JIRA] Created: (JBIDE-1271) Visual Editor should use resource bundles for preview

by Gavin King (JIRA)

Visual Editor should use resource bundles for preview ----------------------------------------------------- Key: JBIDE-1271 URL: http://jira.jboss.com/jira/browse/JBIDE-1271 Project: JBoss Tools Issue Type: Feature Request Reporter: Gavin King It would be a really *great* feature for the VE to automatically fill out any EL expressions which refer to resource bundles strings in the visual preview. It would assume the default locale defined in faces-config (or "en" otherwise). It would pull resources integrated via faces-config, f:loadBundle, or Seam "messages" component. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

10
12
0 / 0

[JBoss JIRA] Created: (JBIDE-1892) Error appears when user deletes selected source in source editor.

by Andrei Scherbovich (JIRA)

Error appears when user deletes selected source in source editor. ----------------------------------------------------------------- Key: JBIDE-1892 URL: http://jira.jboss.com/jira/browse/JBIDE-1892 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.1 Environment: subversion revision 6882. Reporter: Andrei Scherbovich Assigned To: Maxim Areshkau Error appears when user deletes selected source in source editor. See error log in attachment. Steps: 1. EXECUTE: Create JSF KickStart application 2. EXECUTE: Open any file (jsp, xhtml) and press ctrl+A 3. EXECUTE: Press DELETE button 4. FAILURE: error appears -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

5
6
0 / 0

[JBoss JIRA] Created: (JBIDE-699) Re-use of saved launch configurations is not working.

by Gail Nagle (JIRA)

Re-use of saved launch configurations is not working. ----------------------------------------------------- Key: JBIDE-699 URL: http://jira.jboss.com/jira/browse/JBIDE-699 Project: JBoss Tools Issue Type: Bug Components: JBossAS Affects Versions: 2.0.0.Beta2 Environment: Redhat Linux, Eclipse and JBOSS AS package Downloaded as JBossIDE-2.0.0.Beta2-Bundle-linux-gtk.tar Reporter: Gail Nagle Assigned To: Rob Stryker There is a fair amount of effort required to create a launch configuration. In particular, a long list of external jars often must be added. The clear intention of the JBOSS AS IDE is to be able to save, share and generally re-use these configurations. Sharing is further supported by the use of VARIABLE macros in the path of the jars. The IDE adds a project to the Eclipse workspace and the launch configuration is also saved to a file When attempting to re-use the configuration, the IDE detects the existence of these files since it will not allow the creation of a second configuration with the same name. BUT IT WILL NOT RUN THE EXISTING CONFIGURATION. This issue was resolved previously in an earlier version of Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=12898 I recently reported it on http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg17939.html and worked with IBM engineers in Canada to determine that the issue exists in the JBOSS IDE plugin, not in Eclipse itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-2448) ArrayIndexOutOfBoundsException occured after deleting operation

by Tatyana Romanovich (JIRA)

ArrayIndexOutOfBoundsException occured after deleting operation --------------------------------------------------------------- Key: JBIDE-2448 URL: http://jira.jboss.com/jira/browse/JBIDE-2448 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing, UpStream Affects Versions: 2.1.2 Reporter: Tatyana Romanovich Priority: Minor 1. Open any jsp file with content 2. Select whole content and press Delete key on the keyboard Result: ArrayIndexOutOfBoundsException occurred -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 9 months

4
6
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 2008