May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11742) Run as Run on Server - POH5 archetype, does not have Context root set correctly

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11742: ----------------------------------- Summary: Run as Run on Server - POH5 archetype, does not have Context root set correctly Key: JBIDE-11742 URL: https://issues.jboss.org/browse/JBIDE-11742 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Priority: Critical Beta3 internal build - Run As Run on Server using the POH5 archetype does not load the Eclipse browser with http://localhost:8080/poh5, it uses simply http://localhost:8080 http://screencast.com/t/tU3hR5yaYV For some reason the Web Project Settings - Context Root is set to "/" when it should be "poh5". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11605) Central Quickstarts and project update for JDK7 Compiler compliance level in JBDS5

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11605: ------------------------------------ Summary: Central Quickstarts and project update for JDK7 Compiler compliance level in JBDS5 Key: JBIDE-11605 URL: https://issues.jboss.org/browse/JBIDE-11605 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Jiri Peterka Assignee: Radim Hopp It's needed to test Project templates and quickstarts from Central page with JDK7 Current scenario: 1. Import 2. Build 3. Deploy There should be support for a compilation level 1.7 added. Scenario will be this 1. Import/create project 2. Set Compiler level for app to 1.7 3. Build and deploy -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] Created: (JBDS-1587) retro1

by mark yarborough (JIRA)

retro1 ------ Key: JBDS-1587 URL: https://issues.jboss.org/browse/JBDS-1587 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Program Reporter: mark yarborough Assignee: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
4
0 / 0

[JBoss JIRA] (JBDS-2110) Welcome central link is not aligned properly in horizontal view

by Jiri Peterka (JIRA)

Jiri Peterka created JBDS-2110: ---------------------------------- Summary: Welcome central link is not aligned properly in horizontal view Key: JBDS-2110 URL: https://issues.jboss.org/browse/JBDS-2110 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Welcome Affects Versions: 5.0.0.Beta3 Environment: JBDS 5.0.0.Beta3, #119, L64 Reporter: Jiri Peterka Priority: Minor Fix For: 5.0.0.CR1 Welcome view is not aligning link to Central properly when open as horizontal (see screnshot) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11887) NPE when renaming runtime and then rightclicking on server before saving server editor

by Martin Malina (JIRA)

Martin Malina created JBIDE-11887: ------------------------------------- Summary: NPE when renaming runtime and then rightclicking on server before saving server editor Key: JBIDE-11887 URL: https://issues.jboss.org/browse/JBIDE-11887 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: JBDS 5.0 Beta3b (H140) JBoss AS 7.1.1.Final Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.0.CR1 When you rename a runtime but the server doesn't know about the change yet and you right-click on the server in server view, you will get a NPE. Perhaps the affected servers can be notified when the runtime is renamed and their runtime settings can be modified automatically? Or at least the error should be comprehensive and say what's wrong. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11820) Default classpath entries preference page fails for many reasons

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11820: ----------------------------------- Summary: Default classpath entries preference page fails for many reasons Key: JBIDE-11820 URL: https://issues.jboss.org/browse/JBIDE-11820 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.CR1 When using the default classpath entry preference page (under "runtimes" in the preference page section), use the combo to select some runtime type like as7. When the viewer fills up, note the following: 1) Click on an entry in the middle (not top or bottom entry): NPE 2) Click 'add' - note "name" entry is not used, confusing for a user 3) Click 'add' - note default folder is blank and not useful 4) Click 'add' - note that titles and descriptions are not very good 5) Click 'add' - note that default includes pattern is **/*.xml, not relevant for classpath -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11809) Exceptions when trying to edit the default classpath for runtimes

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11809: ------------------------------------------- Summary: Exceptions when trying to edit the default classpath for runtimes Key: JBIDE-11809 URL: https://issues.jboss.org/browse/JBIDE-11809 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Rydahl Andersen click around on AS 7.1 filesets and I eventually get NPE's like the following: java.lang.NullPointerException at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:63) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:60) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:56) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.equals(Fileset.java:149) at org.eclipse.jface.viewers.StructuredViewer.equals(StructuredViewer.java:727) at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2696) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1908) at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1883) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1840) at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1826) at org.eclipse.jface.viewers.StructuredViewer$7.run(StructuredViewer.java:1508) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1506) at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:537) at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1465) at org.jboss.ide.eclipse.as.ui.preferences.ServerTypePreferencePage$AbstractComboDataPreferenceComposite$2.widgetSelected(ServerTypePreferencePage.java:129) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3613) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) java.lang.NullPointerException at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:63) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:60) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.getFolder(Fileset.java:56) at org.jboss.ide.eclipse.archives.webtools.filesets.Fileset.equals(Fileset.java:149) at java.util.ArrayList.indexOf(ArrayList.java:216) at org.jboss.ide.eclipse.as.ui.preferences.ServerTypePreferencePage$AbstractComboDataPreferenceComposite.updateMoveUpMoveDown(ServerTypePreferencePage.java:162) at org.jboss.ide.eclipse.as.ui.preferences.ServerTypePreferencePage$AbstractComboDataPreferenceComposite.handleViewerSelectionChanged(ServerTypePreferencePage.java:144) at org.jboss.ide.eclipse.as.ui.preferences.ServerTypePreferencePage$AbstractComboDataPreferenceComposite$1.selectionChanged(ServerTypePreferencePage.java:114) at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:164) 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.Viewer.fireSelectionChanged(Viewer.java:162) at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2188) at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1211) at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1241) at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:239) at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:233) at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:403) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4128) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1457) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1480) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1465) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1270) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3974) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4875) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1092) at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2052) at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1084) at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2528) at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2007) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5471) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220) at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2095) at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2253) at org.eclipse.swt.widgets.Display.windowProc(Display.java:5535) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4989) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5138) 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:3610) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:178) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.runCommand(CocoaUIEnhancer.java:393) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:535) at org.eclipse.ui.internal.cocoa.CocoaUIEnhancer.actionProc(CocoaUIEnhancer.java:520) at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method) at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4879) at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5226) at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method) at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(NSApplication.java:94) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3607) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
3
0 / 0

[JBoss JIRA] (JBIDE-11297) AS7 ability to add deployment folders on separate file systems

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11297: ----------------------------------- Summary: AS7 ability to add deployment folders on separate file systems Key: JBIDE-11297 URL: https://issues.jboss.org/browse/JBIDE-11297 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta2 Servers earlier than as7 have a management task which can be called to add an arbitrary folder as one that the deployment scanner should scan. Ensure that jbosstools can make use of this for as7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
7
0 / 0

[JBoss JIRA] (JBDS-2139) Errors in console after starting installer

by Martin Malina (JIRA)

Martin Malina created JBDS-2139: ----------------------------------- Summary: Errors in console after starting installer Key: JBDS-2139 URL: https://issues.jboss.org/browse/JBDS-2139 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.Beta3 Environment: jbdevstudio-product-universal-5.0.0.v201205101833M-H138-Beta3.ja Reporter: Martin Malina Fix For: 5.0.0.CR1 Right after starting the installer using: java -jar jbdevstudio-product-universal-5.0.0.v201205101833M-H138-Beta3.ja I get these errors in the console: May 14 11:30:56 vokuro.brq.redhat.com java[8360] <Error>: CGContextGetCTM: invalid context 0x0 May 14 11:30:56 vokuro.brq.redhat.com java[8360] <Error>: CGContextSetBaseCTM: invalid context 0x0 May 14 11:30:56 vokuro.brq.redhat.com java[8360] <Error>: CGContextGetCTM: invalid context 0x0 May 14 11:30:56 vokuro.brq.redhat.com java[8360] <Error>: CGContextSetBaseCTM: invalid context 0x0 Can we get rid of those somehow? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-11587) Users getting confused by rse launch tab

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11587: ----------------------------------- Summary: Users getting confused by rse launch tab Key: JBIDE-11587 URL: https://issues.jboss.org/browse/JBIDE-11587 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta3 Users and QE and even I am getting confused by the several tabs which seem to not relate to each other. When a server is in RSE mode, the launch tab group should only show the RSE tab. When a server is in local mode, it should only show local-relative tabs. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
5
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 May 2012