[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17696:
---------------------------------------
There should be output that looks like one below:
{code}[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) will yieldRule to JPA Project Change Event Handler(1815)
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) will yieldRule to JPA Project Change Event Handler(1815)
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) is waiting for JPA Project Change Event Handler(1815) to transition from WAITING state
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) waiting to resume
[Thread[Worker-15,5,main]]Enabling Maven Dependency Management(1810) resumed{code}
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17696:
----------------------------------
Attachment: .options
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: .options, jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17696) Enabling Maven Dependency Management job waits forever
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17696?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17696:
---------------------------------------
It looks like ether GraphUpdateJob issue of JobManager.yieldRule issue for further debugging would be good to see job yielding tracing output, to enable that you need:
# .option file (see attachment)
# run eclipse with '-consoleLog -debug /path/to/the/.option'
Try to replicate the error again and attach console output to this issue.
Thanks.
> Enabling Maven Dependency Management job waits forever
> ------------------------------------------------------
>
> Key: JBIDE-17696
> URL: https://issues.jboss.org/browse/JBIDE-17696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta2
> Environment: OpenJDK 1.7, 64b
> Ubuntu 12.04, 64b
> Reporter: Rastislav Wagner
> Fix For: 4.2.x
>
> Attachments: jstack1.out, jstack2.out, jstack_mvn.out, mvn.png, wait1.png, wait2.png
>
>
> I dont have exact steps to reproduce because this usually occurs after longer work. I'm testing various configurators (CDI/Seam/JAXRS..) using this scenario:
> 1. Create Dynamic Web Project
> 2. Convert to maven project (using Configure -> Convert to maven..)
> 3. Add some dependency
> 4. check if proper facet was enabled
> 5. delete project and repeat
> After trying this 10-15 times (sometimes more, sometimes less), during step 2 "Enabling Maven Dependency Management" job is waiting and never ends - see screenshot - there's always "Setting classpath containers".
> JVM thread dump attached.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17737:
--------------------------------------
Assignee: Snjezana Peco
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17737:
-----------------------------------
Component/s: runtime-detection
(was: seam2)
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17737) org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17737?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17737:
-----------------------------------
Fix Version/s: 4.2.0.Beta3
> org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests failure
> --------------------------------------------------------------------------------
>
> Key: JBIDE-17737
> URL: https://issues.jboss.org/browse/JBIDE-17737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta3
>
> Attachments: org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests.txt
>
>
> {code}
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionAllTests
> 0
> 0
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.265 sec <<< FAILURE!
> Results :
> Failed tests: testJBossAs42(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs51(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> testJBossAs70(org.jboss.tools.runtime.seam.detector.test.SeamRuntimeDetectionTest): expected:<1> but was:<0>
> Tests run: 8, Failures: 3, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17736) org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17736?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-17736:
--------------------------------------
Assignee: Viacheslav Kabanovich
> org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
> -----------------------------------------------------
>
> Key: JBIDE-17736
> URL: https://issues.jboss.org/browse/JBIDE-17736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.CR1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.seam.xml.test.SeamXMLAllTests
> -------------------------------------------------------------------------------
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.651 sec <<< FAILURE!
> testDebugAttribute(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 1.878 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:108)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> testComponentFile(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestNavigationPagesComponent(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXMLModel(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXML23Model(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.033 sec
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17736) org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17736?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17736:
-----------------------------------
Fix Version/s: 4.2.0.CR1
> org.jboss.tools.seam.xml.test.SeamXMLAllTests failure
> -----------------------------------------------------
>
> Key: JBIDE-17736
> URL: https://issues.jboss.org/browse/JBIDE-17736
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.CR1
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.seam.xml.test.SeamXMLAllTests
> -------------------------------------------------------------------------------
> Tests run: 5, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 3.651 sec <<< FAILURE!
> testDebugAttribute(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 1.878 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:108)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.extensions.TestDecorator.basicRun(TestDecorator.java:23)
> at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.extensions.TestSetup.run(TestSetup.java:27)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:86)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3806)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3444)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> testComponentFile(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestNavigationPagesComponent(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXMLModel(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.001 sectestXML23Model(org.jboss.tools.seam.xml.test.SeamXMLModelTest) Time elapsed: 0.033 sec
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17700:
-------------------------------------
[~fbricon] I might need your help on determining if m2e is somehow at fault here.
[~olpf] Can you do a grep on your eclipse installation to see if any other plugins have classworlds in it or is using it? grep -R "classworlds" * should be sufficient. In my installation, only m2e matches.
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17700:
-------------------------------------
I actually can't think of *ANY* reason at all why any thread running in eclipse would have org.codehaus.plexus.classworlds.realm.ClassRealm as its class loader. It would seem to me that eclipse, as an osgi-container basically, should be in charge of the classloaders entirely.
I did a grep on my installation's "plugins" folder, and the only plugins that seem to mention org.codehaus.plexus.classworlds is org.eclipse.m2e.maven.runtime_1.5.0.20140505-1310
Is m2e behaving badly here? Is it setting its classloader and not putting it back?
> Cannot deploy jsf war with eclipse luna and jboss 7.1.x
> -------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Priority: Critical
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months