March 2009 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-1855) Junit tests error under linux x64

by Maxim Areshkau (JIRA)

Junit tests error under linux x64 --------------------------------- Key: JBIDE-1855 URL: http://jira.jboss.com/jira/browse/JBIDE-1855 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Affects Versions: 2.0.1 Environment: Fedora core 8 x64 Reporter: Maxim Areshkau Assigned To: Maxim Areshkau Attachments: AllTests.tar.bz2 Junit tests error when execution tests for VPE. -- 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

16 years, 11 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4000) TestNG failed for Seam Exaple Projects.

by Anton Klimkovich (JIRA)

TestNG failed for Seam Exaple Projects. --------------------------------------- Key: JBIDE-4000 URL: https://jira.jboss.org/jira/browse/JBIDE-4000 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich Assignee: Snjezana Peco EXECUTE: Import Seam Booking or Seam DVD Store exaple projects into workspace EXECUTE: run TestNG (testng.xml exists) FAILURE: TestNG failed for both seam examples projects with similar problem Caused by: java.lang.IllegalArgumentException: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName: java.lang.RuntimeException: Could not create Component: accept at org.jboss.seam.init.Initialization.addComponent(Initialization.java:989) at org.jboss.seam.init.Initialization.installComponents(Initialization.java:911) at org.jboss.seam.init.Initialization.init(Initialization.java:589) at org.jboss.seam.mock.BaseSeamTest.startSeam(BaseSeamTest.java:939) at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:923) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:167) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:104) at org.testng.TestRunner.runWorkers(TestRunner.java:712) at org.testng.TestRunner.privateRun(TestRunner.java:582) at org.testng.TestRunner.run(TestRunner.java:477) at org.testng.SuiteRunner.runTest(SuiteRunner.java:324) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:319) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823) at org.testng.TestNG.runSuitesLocally(TestNG.java:790) at org.testng.TestNG.run(TestNG.java:708) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) Caused by: java.lang.IllegalArgumentException: You must specify org.jboss.seam.core.init.jndiPattern or use @JndiName: accept at org.jboss.seam.Component.getJndiName(Component.java:438) at org.jboss.seam.Component.<init>(Component.java:243) at org.jboss.seam.Component.<init>(Component.java:217) at org.jboss.seam.init.Initialization.addComponent(Initialization.java:974) ... 27 more EXECUTE: Import Seam Booking Example - War Standalone EXECUTE: run TestNG (testng.xml exists) FAILURE: TestNG failed wit another exception: javax.servlet.ServletException: ServletContext not allow to getResourceAsStream for /WEB-INF/web.xml at org.ajax4jsf.webapp.WebXml.init(WebXml.java:120) at org.ajax4jsf.resource.InternetResourceService.init(InternetResourceService.java:133) at org.ajax4jsf.webapp.BaseFilter.init(BaseFilter.java:148) at org.jboss.seam.web.Ajax4jsfFilter.init(Ajax4jsfFilter.java:86) at org.jboss.seam.servlet.SeamFilter.init(SeamFilter.java:97) at org.jboss.seam.mock.BaseSeamTest.createSeamFilter(BaseSeamTest.java:992) at org.jboss.seam.mock.BaseSeamTest.setupClass(BaseSeamTest.java:965) at org.jboss.seam.mock.BaseSeamTest.init(BaseSeamTest.java:924) at org.jboss.seam.mock.SeamTest.init(SeamTest.java:42) 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.testng.internal.MethodHelper.invokeMethod(MethodHelper.java:580) at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:398) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:145) at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:82) at org.testng.internal.TestMethodWorker.invokeBeforeClassMethods(TestMethodWorker.java:167) at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:104) at org.testng.TestRunner.runWorkers(TestRunner.java:712) at org.testng.TestRunner.privateRun(TestRunner.java:582) at org.testng.TestRunner.run(TestRunner.java:477) at org.testng.SuiteRunner.runTest(SuiteRunner.java:324) at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:319) at org.testng.SuiteRunner.privateRun(SuiteRunner.java:292) at org.testng.SuiteRunner.run(SuiteRunner.java:198) at org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:823) at org.testng.TestNG.runSuitesLocally(TestNG.java:790) at org.testng.TestNG.run(TestNG.java:708) at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:73) at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:124) -- 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

16 years, 11 months

3
10
0 / 0

[JBoss JIRA] Created: (JBIDE-3979) Seam markers have invalid type

by Snjezana Peco (JIRA)

Seam markers have invalid type ------------------------------ Key: JBIDE-3979 URL: https://jira.jboss.org/jira/browse/JBIDE-3979 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.0.0.GA Reporter: Snjezana Peco Seam markers are of the type org.eclipse.wst.validation.problemmarker that is invalid. I suppose the issue is caused by fixing JBIDE-3701 or JBIDE-3336. See the attached screenshots. -- 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

16 years, 11 months

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-3909) Exception is thrown in CSSClassDialog

by Denis Maliarevich (JIRA)

Exception is thrown in CSSClassDialog ------------------------------------- Key: JBIDE-3909 URL: https://jira.jboss.org/jira/browse/JBIDE-3909 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.CR2 Reporter: Denis Maliarevich Assignee: Maxim Areshkau Fix For: 3.1.0 Steps to reproduce: 1. Open any css file. 2. Open CSS Class dialog. 3. On "Text/Font" tab in some fields (for example, "Font Style") enter incorrect symbols like ";;;;;;". 4. Click "Apply" or "OK" button. 5. Exceprion is thrown Stack trace: org.w3c.dom.DOMException: at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueTextCore(CSSStyleDeclItemImpl.java:252) at org.eclipse.wst.css.core.internal.document.CSSStyleDeclItemImpl.setCssValueText(CSSStyleDeclItemImpl.java:233) at org.eclipse.wst.css.core.internal.document.CSSStyleDeclarationImpl.setProperty(CSSStyleDeclarationImpl.java:267) at org.jboss.tools.jst.jsp.outline.cssdialog.common.CSSModel.setCSS(CSSModel.java:289) at org.jboss.tools.jst.jsp.outline.cssdialog.CSSClassDialog.saveChanges(CSSClassDialog.java:807) at org.jboss.tools.jst.jsp.outline.cssdialog.CSSClassDialog.close(CSSClassDialog.java:851) at org.eclipse.jface.dialogs.Dialog.okPressed(Dialog.java:940) at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.jboss.tools.jst.jsp.outline.cssdialog.OpenCSSDialogActionDelegate.run(OpenCSSDialogActionDelegate.java:64) at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3823) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3422) 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:386) 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

16 years, 11 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-4104) NPE using s:foramattedText. VPE autorefresh is broken.

by Yura Zhishko (JIRA)

NPE using s:foramattedText. VPE autorefresh is broken. ------------------------------------------------------ Key: JBIDE-4104 URL: https://jira.jboss.org/jira/browse/JBIDE-4104 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor Templates Affects Versions: 3.1.0 Reporter: Yura Zhishko Assignee: Denis Maliarevich 1) Insert s:formattedText into any place of xhtml page (may use attached page) org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException) at org.eclipse.swt.SWT.error(SWT.java:3777) at org.eclipse.swt.SWT.error(SWT.java:3695) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3800) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3425) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2384) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2348) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2200) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:495) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:490) 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:386) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) Caused by: java.lang.NullPointerException at java.io.StringReader.<init>(Unknown Source) at org.jboss.tools.jsf.vpe.seam.template.SeamFormattedTextTemplate.create(SeamFormattedTextTemplate.java:67) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:477) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:272) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addChildren(VpeVisualDomBuilder.java:659) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.createNode(VpeVisualDomBuilder.java:571) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.addNode(VpeVisualDomBuilder.java:272) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateElement(VpeVisualDomBuilder.java:1033) at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.updateNode(VpeVisualDomBuilder.java:963) at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:628) at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:487) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:94) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:133) ... 22 more -- 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

16 years, 11 months

4
9
0 / 0

[JBoss JIRA] Created: (JBIDE-4090) Simple XML files shouldn't be opened with Smooks Editor by default.

by Anton Klimkovich (JIRA)

Simple XML files shouldn't be opened with Smooks Editor by default. ------------------------------------------------------------------- Key: JBIDE-4090 URL: https://jira.jboss.org/jira/browse/JBIDE-4090 Project: Tools (JBoss Tools) Issue Type: Bug Components: XML Structured Editor Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich EXECUTE: Create seam web project EXECUTE: Open seamWeb-ds.xml ASSERT: File should be opened with default XML Editor FAILURE: File is opened with Smooks Editor by default. EXECUTE: Create any xml file FAILURE: File is opened with Smooks Editor by default. All XML files that are not specified with special JBoss Editors are opening with Smooks Editor by default. -- 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

16 years, 11 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-3858) There is no warning message that the specified target runtime does not contain a valid ESB runtime for ESB version 4.5 in New JBoss ESB Project wizard.

by Anton Klimkovich (JIRA)

There is no warning message that the specified target runtime does not contain a valid ESB runtime for ESB version 4.5 in New JBoss ESB Project wizard. ------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-3858 URL: https://jira.jboss.org/jira/browse/JBIDE-3858 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.0.0.GA Reporter: Anton Klimkovich EXECUTE: New-> Project-> JBoss ESB Project EXECUTE: Select esb Version as 4.5 EXECUTE: Select jboss-soa-p.4.3.0 or jbossesb-server 4.4 as Trget Runtime EXECUTE: Press Next button ASSERT: message : the specified target runtime does not contain a valid ESB runtime. Finish button should be disabled. FAILURE: There is no warning message. Finish button is enabled. -- 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

16 years, 11 months

4
11
0 / 0

[JBoss JIRA] Created: (JBIDE-3180) File filters are gone and we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3

by Galder Zamarreno (JIRA)

File filters are gone and we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3 ------------------------------------------------------------------------------------------------------ Key: JBIDE-3180 URL: https://jira.jboss.org/jira/browse/JBIDE-3180 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.beta1 Reporter: Galder Zamarreno Fix For: 3.0.0.cr1 File filters are gone in new server view. Also, we should ship one for conf/jboss-log4j.xml by default for AS/EAP 4.2 or 4.3. -- 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

16 years, 11 months

4
14
0 / 0

[JBoss JIRA] Created: (JBIDE-4045) ArchivesModuleModelListener not registered

by Rob Stryker (JIRA)

ArchivesModuleModelListener not registered ------------------------------------------ Key: JBIDE-4045 URL: https://jira.jboss.org/jira/browse/JBIDE-4045 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.0.0.GA Reporter: Rob Stryker Fix For: 3.0.1.GA, 3.1.0 The non-registration of this listener *only* affects the situation when you right-click on an archive and select "Edit Publish Settings..." and auto-deploy to selected servers is selected. Basically, it's not registered as a listener, and so it doesn't auto-publish. Workaround is, of course, to press the publish button. I think it's high time for some unit tests -- 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

16 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-592) when deleting project exceptions occur

by Max Andersen (JIRA)

when deleting project exceptions occur -------------------------------------- Key: JBIDE-592 URL: http://jira.jboss.com/jira/browse/JBIDE-592 Project: JBoss Tools Issue Type: Bug Components: Seam Affects Versions: 2.0.0.Beta2 Reporter: Max Andersen Assigned To: Denis Golovin delete a project with seam nature and the following happens: java.lang.NullPointerException at org.jboss.tools.seam.ui.views.RootContentProvider$ResourceChangeListener.resourceChanged(RootContentProvider.java:162) at org.eclipse.core.internal.events.NotificationManager$2.run(NotificationManager.java:282) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:276) at org.eclipse.core.internal.events.NotificationManager.handleEvent(NotificationManager.java:260) at org.eclipse.core.internal.resources.Workspace.broadcastEvent(Workspace.java:305) at org.eclipse.core.internal.resources.Resource.unprotectedDelete(Resource.java:1662) at org.eclipse.core.internal.resources.Resource.delete(Resource.java:700) at org.eclipse.core.internal.resources.Project.delete(Project.java:289) at org.eclipse.ui.ide.undo.WorkspaceUndoUtil.delete(WorkspaceUndoUtil.java:578) at org.eclipse.ui.ide.undo.WorkspaceUndoUtil.delete(WorkspaceUndoUtil.java:172) at org.eclipse.ui.ide.undo.AbstractResourcesOperation.delete(AbstractResourcesOperation.java:111) at org.eclipse.ui.ide.undo.DeleteResourcesOperation.doExecute(DeleteResourcesOperation.java:67) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation$1.run(AbstractWorkspaceOperation.java:206) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1797) at org.eclipse.ui.ide.undo.AbstractWorkspaceOperation.execute(AbstractWorkspaceOperation.java:204) at org.eclipse.ui.actions.DeleteResourceAction$4.run(DeleteResourceAction.java:533) -- 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

16 years, 11 months

4
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 March 2009