[JBoss JIRA] (JBIDE-15616) ConcurrentModificationException in CDICoreBuilder
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15616?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-15616:
-----------------------------------------------
Loading of CDI model is implemented through build. That means that build method can be invoked from different threads, one requesting for loaded model, the other performing Eclipse's build. We had already met synchronization problems caused by concurrent access to build, and tried to solve it with improving thread safety. Now, I think, we just cannot allow for concurrent build to happen. One build should wait for the other other.
> ConcurrentModificationException in CDICoreBuilder
> -------------------------------------------------
>
> Key: JBIDE-15616
> URL: https://issues.jboss.org/browse/JBIDE-15616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> testSwitchingCDICapabilities(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.044 sec <<< ERROR!
> org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build.
> at org.eclipse.core.internal.resources.Project$1.run(Project.java:620)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
> at org.eclipse.core.internal.resources.Project.build(Project.java:114)
> at org.jboss.tools.cdi.core.test.DependentProjectTest.testSwitchingCDICapabilities(DependentProjectTest.java:338)
> 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:606)
> 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:606)
> 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:85)
> 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:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Contains: Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'CDITest2'.
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926)
> at java.util.HashMap$KeyIterator.next(HashMap.java:960)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.copy(DefinitionContext.java:85)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.newWorkingCopy(DefinitionContext.java:359)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:204)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
> at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
> at org.eclipse.core.internal.resources.Project.build(Project.java:114)
> at org.jboss.tools.cdi.core.test.DependentProjectTest.testSwitchingCDICapabilities(DependentProjectTest.java:338)
> 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:606)
> 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:606)
> 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:85)
> 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:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15616) ConcurrentModificationException in CDICoreBuilder
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15616?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15616 at 10/10/13 7:12 PM:
-------------------------------------------------------------------------
Loading of CDI model is implemented through build. That means that build method can be invoked from different threads, one requesting for loaded model, the other performing Eclipse's build. We had already met synchronization problems caused by concurrent access to build, and tried to solve it with improving thread safety. Now, I think, we just cannot allow for concurrent build to happen. One build should wait for the other.
was (Author: scabanovich):
Loading of CDI model is implemented through build. That means that build method can be invoked from different threads, one requesting for loaded model, the other performing Eclipse's build. We had already met synchronization problems caused by concurrent access to build, and tried to solve it with improving thread safety. Now, I think, we just cannot allow for concurrent build to happen. One build should wait for the other other.
> ConcurrentModificationException in CDICoreBuilder
> -------------------------------------------------
>
> Key: JBIDE-15616
> URL: https://issues.jboss.org/browse/JBIDE-15616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.0.Alpha1
>
>
> {code}
> testSwitchingCDICapabilities(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.044 sec <<< ERROR!
> org.eclipse.core.internal.resources.ResourceException: Errors occurred during the build.
> at org.eclipse.core.internal.resources.Project$1.run(Project.java:620)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
> at org.eclipse.core.internal.resources.Project.build(Project.java:114)
> at org.jboss.tools.cdi.core.test.DependentProjectTest.testSwitchingCDICapabilities(DependentProjectTest.java:338)
> 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:606)
> 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:606)
> 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:85)
> 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:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Contains: Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'CDITest2'.
> java.util.ConcurrentModificationException
> at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926)
> at java.util.HashMap$KeyIterator.next(HashMap.java:960)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.copy(DefinitionContext.java:85)
> at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.newWorkingCopy(DefinitionContext.java:359)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:204)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:726)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:394)
> at org.eclipse.core.internal.resources.Project$1.run(Project.java:618)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.core.internal.resources.Project.internalBuild(Project.java:597)
> at org.eclipse.core.internal.resources.Project.build(Project.java:114)
> at org.jboss.tools.cdi.core.test.DependentProjectTest.testSwitchingCDICapabilities(DependentProjectTest.java:338)
> 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:606)
> 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:606)
> 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:85)
> 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:135)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/10/13 3:35 PM:
--------------------------------------------------------------------
[~mwigglesworth-redhat] variables view looks good!
3 small suggestions though:
* I'd add the application name in the group title. Without it you dont see what application we're changing the variables for (you only know by the wizard you were just before). "Environment Variables for this Application" -> "Environment Variables for Application XXX"
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
was (Author: adietish):
[~mwigglesworth-redhat] variables view looks good!
3 small suggestions though:
* I add the application name in the group title. Without it you dont see what application we're changing the variables for (you only know by the wizard you were just before). "Environment Variables for this Application" -> "Environment Variables for Application XXX"
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/10/13 3:34 PM:
--------------------------------------------------------------------
[~mwigglesworth-redhat] variables view looks good!
3 small suggestions though:
* I add the application name in the group title. Without it you dont see what application we're changing the variables for (you only know by the wizard you were just before). "Environment Variables for this Application" -> "Environment Variables for Application XXX"
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
was (Author: adietish):
[~mwigglesworth-redhat] variables view looks good!
3 small suggestions though:
* I add the application name in the wizard description are (the white area just below the title, the one with the OpenShift icon on the right). Without it you dont see what application we're changing the variables for.
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-15597 at 10/10/13 3:32 PM:
--------------------------------------------------------------------
[~mwigglesworth-redhat] variables view looks good!
3 small suggestions though:
* I add the application name in the wizard description are (the white area just below the title, the one with the OpenShift icon on the right). Without it you dont see what application we're changing the variables for.
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
was (Author: adietish):
[~mwigglesworth-redhat] variables view looks good!
2 small suggestions though:
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15597) Environmental Variables UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-15597:
------------------------------------------
[~mwigglesworth-redhat] variables view looks good!
2 small suggestions though:
* Why not shorten "Variable Name" to "Name" and "Variable Value" to "Value" (since the table's in a dialog and a group that clearly states that this is about variables)?
* I'd maybe change the column weight, I'm not sure though: Aren't names usually smaller than values? If yes, then I'd have the "Name" column more narrow than the "Value" column
> Environmental Variables UI
> --------------------------
>
> Key: JBIDE-15597
> URL: https://issues.jboss.org/browse/JBIDE-15597
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Martes Wigglesworth
> Priority: Blocker
> Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, jira-JBIDE-15597-newapplication-variables-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-screenshot.jpeg, jira-JBIDE-15597-setupprojectview-variablesbutton-twochoices-screenshot.jpeg, jira-JBIDE-15598-wizard-screenshot.jpeg, manage-keys.png, openshift-newappwizard-config_and_server_settings.jpeg
>
>
> GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBIDE-15641) Unable to change the CDI Facet from 1.0 to 1.1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15641?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15641:
----------------------------------------
Old schema will still work. Updating the beans.xml can be tricky if it uses any extensions there. So I would prefer not to change beans.xml at all.
> Unable to change the CDI Facet from 1.0 to 1.1
> ----------------------------------------------
>
> Key: JBIDE-15641
> URL: https://issues.jboss.org/browse/JBIDE-15641
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.2.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Fix For: 4.2.0.Alpha1
>
>
> - Create a CDI project with Facet 1.0
> - Right-click on project > Properties > Project Facets
> - change the CDI version to 1.1
> => "Cannot change version of project facet CDI (...) to 1.1"
> No indications whatsoever of why you can't change it. Constraints seem ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months
[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2734:
-------------------------------------------
Forge 2 is moved of 7.1 since it is not going to be a full replacement for Forge 1.
JBT 4.1.x will still receive the Forge 2 features, but we are not putting it in as default install for JBDS.
Current Plan is that in JBDS 8 we will use Forge 2 only and Forge 1 will be deprecated but still possible to install.
> Forge 2 in JBDS
> ---------------
>
> Key: JBDS-2734
> URL: https://issues.jboss.org/browse/JBDS-2734
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: forge, requirements
> Reporter: Burr Sutter
> Fix For: 8.0.0.GA
>
>
> Is Forge 2 ready to be included in JBDS ?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months