[JBoss JIRA] Created: (JBIDE-6489) org.jboss.ide.eclipse.as.test.publishing.JBIDE2512bTest throws OutOfMemoryError: PermGen space
by Nick Boldt (JIRA)
org.jboss.ide.eclipse.as.test.publishing.JBIDE2512bTest throws OutOfMemoryError: PermGen space
----------------------------------------------------------------------------------------------
Key: JBIDE-6489
URL: https://jira.jboss.org/browse/JBIDE-6489
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.2.0.M1
Reporter: Nick Boldt
Assignee: Rob Stryker
Running org.jboss.ide.eclipse.as.test.ASTestSuite
2010-06-17 19:33:41.785:INFO::Logging to StdErrLog::DEBUG=false via org.eclipse.jetty.util.log.StdErrLog
Unable to set nested messages property.
Tests run: 28, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 28.01 sec <<< FAILURE!
testJBIDE2512b(org.jboss.ide.eclipse.as.test.publishing.JBIDE2512bTest) Time elapsed: 2.873 sec <<< FAILURE!
junit.framework.AssertionFailedError: URI is null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:214)
at org.jboss.ide.eclipse.as.test.publishing.JBIDE2512bTest.testJBIDE2512b(JBIDE2512bTest.java:38)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
testJBIDE2512b(org.jboss.ide.eclipse.as.test.publishing.JBIDE2512bTest)
Exception in thread "WorkbenchTestable" org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.OutOfMemoryError: PermGen space)
http://hudson.qa.jboss.com/hudson/view/DevStudio_Tycho/job/jbosstools-3.2...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months
[JBoss JIRA] Created: (JBIDE-6122) Refactor->Rename for web module in seam ear project throws an exception
by Denis Golovin (JIRA)
Refactor->Rename for web module in seam ear project throws an exception
-----------------------------------------------------------------------
Key: JBIDE-6122
URL: https://jira.jboss.org/jira/browse/JBIDE-6122
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam, UpStream
Affects Versions: 3.1.0.GA
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 3.6-Helios
Create seam project in EAR deployment and try to Refactor->Rename... Dynamic Web Project. Exception below is thrown:
java.lang.ClassCastException: org.eclipse.jst.j2ee.refactor.operations.ProjectRefactorMetadata$RefCachingVirtualComponent cannot be cast to org.eclipse.jst.j2ee.componentcore.util.EARVirtualComponent
at org.eclipse.jst.j2ee.application.internal.operations.AddComponentToEnterpriseApplicationOp.moduleClasspathForceUpdate(AddComponentToEnterpriseApplicationOp.java:308)
at org.eclipse.jst.j2ee.application.internal.operations.AddComponentToEnterpriseApplicationOp.execute(AddComponentToEnterpriseApplicationOp.java:78)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.jst.j2ee.refactor.operations.UpdateDependentEARonRenameOp.execute(UpdateDependentEARonRenameOp.java:78)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.jst.j2ee.refactor.operations.ProjectRenameOperation.updateDependentEARProject(ProjectRenameOperation.java:154)
at org.eclipse.jst.j2ee.refactor.operations.ProjectRefactorOperation.updateDependentProjects(ProjectRefactorOperation.java:92)
at org.eclipse.jst.j2ee.refactor.operations.ProjectRenameOperation.updateDependentProjects(ProjectRenameOperation.java:137)
at org.eclipse.jst.j2ee.refactor.operations.ProjectRefactorOperation.execute(ProjectRefactorOperation.java:58)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl$1.run(DataModelPausibleOperationImpl.java:376)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:401)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.runOperation(DataModelPausibleOperationImpl.java:352)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.doExecute(DataModelPausibleOperationImpl.java:242)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.executeImpl(DataModelPausibleOperationImpl.java:214)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.cacheThreadAndContinue(DataModelPausibleOperationImpl.java:89)
at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelPausibleOperationImpl.execute(DataModelPausibleOperationImpl.java:202)
at org.eclipse.jst.j2ee.refactor.listeners.ProjectRefactoringListener$1.runInWorkspace(ProjectRefactoringListener.java:188)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBIDE-6653) new process definitions cannot be created in "empty" projects
by Marcel Sebek (JIRA)
new process definitions cannot be created in "empty" projects
-------------------------------------------------------------
Key: JBIDE-6653
URL: https://jira.jboss.org/browse/JBIDE-6653
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.1.1
Reporter: Marcel Sebek
Assignee: Koen Aers
I have an "empty" eclipse project with a custom ant script for building and deploying .par files. I can edit the contained process definitions in eclipse but I cannot create new processes. When I try to, I get "Source folder is not valid" message. The only workaround I've found is to create the process definition in another project (eg. an ejb jar) and then move the process to the correct project.
In my opinion, there is no reason to restrict creating process definitions to some type of projects only.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 7 months