Hi Achim, Short answer:
They do work separately. "test" comes before "package", "integration-test" comes after "package", and this is what I need. Long answer: There is a Maven project regression-pde-bundle which I need in my tests for the "reference:" protocol in 3 different shapes, as a JAR, as an exploded directory, and as a directory in the special PDE layout. The regression-paxrunner project uses the maven-dependency-plugin to unpack the regression-pde-bundle before running the tests. Of course, unpacking requires that things have been packaged. Everything works fine when you do "mvn clean install", which I checked before committing. But when you only run "mvn clean test", regression-pde-bundle has not been packaged, and in regression-paxrunner, the maven-dependency-plugin tries to unpack the ../regression-pde-bundle/target/classes classpath component. Running "mvn clean integration-test" ensures that the dependencies have been packaged. The tests in regression-paxrunner continue to run in the "test" phase, not the "integration-test" phase. This might change in the long run - in fact, with the reference: protocol, the answer to the FAQ "Why do I need a separate project to run my tests?" may change. Cheers, Harald > == Achim wrote: == just my 2 cents here, but shouldn't test and integration-test work separately? I would expect that test works and itest also, but not that the one is dependent on the other :-) -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
