David Sean Taylor wrote:
Im building from the cvs head and the build (with tests) is failing, but only with maven allClean allBuild.
When I cd to /portal and build there (maven test), the test passes.
Anyone else seeing this one?
Yes. Same error here. I noticed though that this happens on the second test run done by maven. The first time, it passes. That may explain why you can build it from /portal directly too. I don't no why maven insist on running the test twice but I guess it has something to do with the multi-project functionality. It would be nice if we could clean up this build mess sometime. I've looked at it in the past and remember disabling this double test run once, but as our build procedure has significantly changed again since then I'm at the moment lost how to fix this again, and to be honest also quite annoyed with maven so I don't have much appetite to look into it right now :-( Anyway, it seems the TestSimpleDeployment cannot handle to be run twice without a clean up of the target directory.
Testcase: testUndeployVersusRedeploy(org.apache.jetspeed.deployment.TestSimpleDeployment): FAILED
null
junit.framework.AssertionFailedError
at org.apache.jetspeed.deployment.TestSimpleDeployment.testUndeployVersusRedeploy(TestSimpleDeployment.java:278)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:2
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
