[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-2418) fix errors in archives.test related to build properties
Max Rydahl Andersen (JIRA)
jira-events at lists.jboss.org
Fri Aug 8 10:51:52 EDT 2008
[ https://jira.jboss.org/jira/browse/JBIDE-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Max Rydahl Andersen resolved JBIDE-2418.
----------------------------------------
Fix Version/s: 3.0.0.alpha
(was: 3.0.0.beta1)
Resolution: Done
> fix errors in archives.test related to build properties
> -------------------------------------------------------
>
> Key: JBIDE-2418
> URL: https://jira.jboss.org/jira/browse/JBIDE-2418
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Affects Versions: 3.0.0.alpha
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 3.0.0.alpha
>
>
> Several resources are missing in binary test distribution as example:
> Model failed to save when it should have saved. /qa/services/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806211803-nightly/tests/eclipse/plugins/org.jboss.ide.eclipse.archives.test_1.0.0/output/test.xml (No such file or directory)
> junit.framework.AssertionFailedError: Model failed to save when it should have saved. /qa/services/hudson/hudson_workspace/workspace/jbosstools-nightly/jbds-build/200806211803-nightly/tests/eclipse/plugins/org.jboss.ide.eclipse.archives.test_1.0.0/output/test.xml (No such file or directory)
> at org.jboss.ide.eclipse.archives.test.model.XBMarshallTest.write(XBMarshallTest.java:121)
> at org.jboss.ide.eclipse.archives.test.model.XBMarshallTest.writeFileset(XBMarshallTest.java:210)
> at org.jboss.ide.eclipse.archives.test.model.XBMarshallTest.testWriteFilesetSuccess(XBMarshallTest.java:214)
> at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354)
> at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206)
> at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35)
> at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31)
> at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:574)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1212)
> at org.eclipse.core.launcher.Main.main(Main.java:30)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list