[JBoss JIRA] (JBIDE-11164) Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11164?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky updated JBIDE-11164:
--------------------------------------
Fix Version/s: 3.3.2.Final
(was: 3.3.x)
> Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-11164
> URL: https://issues.jboss.org/browse/JBIDE-11164
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 3.3.0.Beta1
> Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-29_14-32-12-H100.zip,L64
> Reporter: Jiri Peterka
> Assignee: Andrej Podhradsky
> Priority: Minor
> Fix For: 3.3.0.Beta3, 3.3.2.Final
>
>
> !ENTRY org.eclipse.ui.workbench 4 0 2012-03-05 13:27:01.277
> !MESSAGE Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> !STACK 0
> java.lang.RuntimeException: Widget disposed too early for part org.jboss.tools.central.editors.JBossCentralEditor
> at org.eclipse.ui.internal.WorkbenchPartReference$1.widgetDisposed(WorkbenchPartReference.java:171)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:123)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1263)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1080)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:1294)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:1083)
> at org.eclipse.swt.widgets.Control.release(Control.java:3488)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:462)
> at org.eclipse.ui.internal.EditorSashContainer.disposeParent(EditorSashContainer.java:195)
> at org.eclipse.ui.internal.PartSashContainer.dispose(PartSashContainer.java:599)
> at org.eclipse.ui.internal.EditorSashContainer.dispose(EditorSashContainer.java:187)
> at org.eclipse.ui.internal.EditorAreaHelper.dispose(EditorAreaHelper.java:125)
> at org.eclipse.ui.internal.WorkbenchPage.dispose(WorkbenchPage.java:1898)
> at org.eclipse.ui.internal.WorkbenchWindow.closeAllPages(WorkbenchWindow.java:894)
> at org.eclipse.ui.internal.WorkbenchWindow.hardClose(WorkbenchWindow.java:1729)
> at org.eclipse.ui.internal.WorkbenchWindow.busyClose(WorkbenchWindow.java:730)
> at org.eclipse.ui.internal.WorkbenchWindow.access$0(WorkbenchWindow.java:715)
> at org.eclipse.ui.internal.WorkbenchWindow$6.run(WorkbenchWindow.java:867)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.WorkbenchWindow.close(WorkbenchWindow.java:865)
> at org.eclipse.jface.window.WindowManager.close(WindowManager.java:109)
> at org.eclipse.ui.internal.Workbench$18.run(Workbench.java:1114)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:1111)
> at org.eclipse.ui.internal.Workbench.access$15(Workbench.java:1040)
> at org.eclipse.ui.internal.Workbench$25.run(Workbench.java:1284)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1282)
> at org.eclipse.ui.internal.Workbench.close(Workbench.java:1254)
> at org.eclipse.ui.internal.testing.WorkbenchTestable$2.run(WorkbenchTestable.java:124)
> 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:3563)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3212)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
> at org.eclipse.swtbot.eclipse.core.UITestApplication.start(UITestApplication.java:54)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1386)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15482:
----------------------------------------
> I don't see the difference, because mirroring would fail anyway
Actually, it would rarely (never?) fail. The issue which causes builds to fail is that Tycho appears to first fetch metadata, and fetch dependencies later, which create a delay where site can disappear. If we mirror first, the delay is much shorter, so we reduce the risk of errors, and moreover, we'd see build failing during this preparation test, making it clear it's not an actual aggregation issue.
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.Alpha1
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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, 4 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-15482:
---------------------------------------
I don's see the difference, because mirroring would fail anyway
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.Alpha1
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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, 4 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-15482 at 11/27/13 1:50 AM:
-----------------------------------------------------------------
I don't see the difference, because mirroring would fail anyway
was (Author: dgolovin):
I don's see the difference, because mirroring would fail anyway
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.Alpha1
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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, 4 months
[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15482:
----------------------------------------
As an alternative implementation, we could think about having the job first mirroring locally the repositories they depend on before they start up, and use a settings.xml to use the local mirror instead of the remote sites.
The benefit is that once stuff is mirrored locally, it won't be removed later.
> Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15482
> URL: https://issues.jboss.org/browse/JBIDE-15482
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.Alpha1
>
>
> Be it proposed:
> {quote}
> that instead of an in-place move which reuses
> generic folder names like "staging" and "staging.previous", we
> composite build output using unique names like
> 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255
> {quote}
> We therefore need:
> a) to regenerate the composite site each time there's a new build
> published, in order to remove the oldest and add the newest (keeping
> only the Nth and N-1rst builds)
> (I have a script that might already work for this, or would need
> tweaking.)
> b) heuristics to determine when an older (N-2, N-3, ... N-z) build is
> no longer needed, perhaps simply by assuming no one needs it after
> 24hrs?
> 24 hours should be more that enough.
> c) a cleanup script which can purge all but the builds which are no
> more than 1 day old, keeping at all times at least two builds (N and
> N-1)
> (I have a script that already does this for folders like
> http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but
> might need to be tweaked to work for a new pattern of
> staging/\$\{JOB_NAME}/<BUILD_ID>/ .)
> {quote}
--
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, 4 months
[JBoss JIRA] (JBIDE-15871) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15871?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15871.
---------------------------------
Resolution: Done
Balls are blue, the world is happy. Contradiction? I think not.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component
> -----------------------------------------------------------
>
> Key: JBIDE-15871
> URL: https://issues.jboss.org/browse/JBIDE-15871
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: server
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Labels: testfailure
> Fix For: 4.1.1.Final
>
>
> *1 Test Failure(s) in JBIDE 4.1.1.Beta1 for server component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> # [org.jboss.tools.as.test.core.parametized.server.publishing.defect.Republi...] (failing for 3 builds)
> [Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for server component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest : testJBIDE6184_Odd_Republish_Error[0]{color} (failing for 3 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-server_41/139/testReport/org.jboss.tools.as.test.core.parametized.server.publishing.defect/RepublishDefectTest/testJBIDE6184_Odd_Republish_Error_0_}
> <case>
> <age>3</age>
> <className>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest</className>
> <duration>7.94</duration>
> <errorDetails>expected:<false> but was:<true></errorDetails>
> <errorStackTrace>junit.framework.AssertionFailedError: expected:<false> but was:<true>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:174)
> at junit.framework.Assert.assertEquals(Assert.java:181)
> at junit.framework.TestCase.assertEquals(TestCase.java:341)
> at org.jboss.tools.as.test.core.parametized.server.publishing.AbstractPublishingTest.verifyList(AbstractPublishingTest.java:362)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.JBIDE6184EarHasDynProjs(RepublishDefectTest.java:137)
> at org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest.testJBIDE6184_Odd_Republish_Error(RepublishDefectTest.java:111)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> at org.junit.runners.Suite.runChild(Suite.java:127)
> at org.junit.runners.Suite.runChild(Suite.java:26)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: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)
> </errorStackTrace>
> <failedSince>137</failedSince>
> <name>testJBIDE6184_Odd_Republish_Error[0]</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>org.jboss.tools.as.test.core.parametized.server.publishing.defect.RepublishDefectTest: org.jboss.ide.eclipse.as.systemCopyServer, zipped, metadata, permod_default
> /mnt/hudson_workspace/workspace/jbosstools-server_41/sources/as/tests/org.jboss.tools.as.test.core/target/work/data/.metadata/.plugins/org.jboss.tools.as.test.core/testDeployments/1383068483553/deploy/ear1.ear
> </stdout>
> </case>
> {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, 4 months
[JBoss JIRA] (TOOLSDOC-384) Technical Review of 7.0 User Guide
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-384?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-384:
-------------------------------------
Description:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools *[done]*
* LiveReload Tools *[done]*
* Mobile Web Tools
* BrowserSim
* OpenShift Tools
was:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools *[done]*
* LiveReload Tools
* Mobile Web Tools
* BrowserSim
* OpenShift Tools
> Technical Review of 7.0 User Guide
> ----------------------------------
>
> Key: TOOLSDOC-384
> URL: https://issues.jboss.org/browse/TOOLSDOC-384
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
> * JBoss Central and the JBoss Perspective *[done]*
> * JBoss Server Tools *[done]*
> * Forge Tools *[done]*
> * LiveReload Tools *[done]*
> * Mobile Web Tools
> * BrowserSim
> * OpenShift Tools
--
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, 4 months
[JBoss JIRA] (TOOLSDOC-384) Technical Review of 7.0 User Guide
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-384?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-384:
-------------------------------------
Description:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools *[done]*
* LiveReload Tools
* Mobile Web Tools
* BrowserSim
* OpenShift Tools
was:
Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
* JBoss Central and the JBoss Perspective *[done]*
* JBoss Server Tools *[done]*
* Forge Tools
* LiveReload Tools
* Mobile Web Tools
* BrowserSim
* OpenShift Tools
> Technical Review of 7.0 User Guide
> ----------------------------------
>
> Key: TOOLSDOC-384
> URL: https://issues.jboss.org/browse/TOOLSDOC-384
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: User Guide
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.0
>
>
> Conduct a post release technical review of 7.0 User Guide to catch any previously missed technical or copy errors.
> * JBoss Central and the JBoss Perspective *[done]*
> * JBoss Server Tools *[done]*
> * Forge Tools *[done]*
> * LiveReload Tools
> * Mobile Web Tools
> * BrowserSim
> * OpenShift Tools
--
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, 4 months