I'm trying to use release:prepare and I get to our last module which is just one that assembles all the binary assemblies of the previous modules into an uber-archive.
The release:prepare fails because if can not locate the binary dependencies: my.group:myartifact:zip:bin:0.2 which is obvious since release:prepare only runs clean, integration-test What is not obvious is why it is trying to resolve these dependencies? Since this is an assembly pom, there is no source code, no test code, no integration tests. I had a similar problem with assembly:attached because it uses @aggregator (I found http://jira.codehaus.org/browse/MASSEMBLY-97 which said to use assembly:single instead) I suspect there is something similar going on here for integration-test. Is there a way to override release:prepare to run install as well? Anyone able to point me at what integration-test runs so I can have a look and maybe debug this a bit? My workaround was to manually run mvn install after the failure and to re-reun mvn release:prepare which picked up from where it failed. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
