Wayne Fay wrote > > If you have problems running tests, then just skip them [1]. > Thanks. Skipping the tests, the build works.
Wayne Fay wrote > > As an aside, I pulled down wagon-2.2 from the tag and had no issues > building > it and running tests. > Right. I did that too, with no change whatsoever to any pom, and it failed in the same place. So, my setting a proxy didn't help (I don't know in detail what this company proxy actually does). Again, skipping tests, the build works. Wayne Fay wrote > > Generally, you should not be invoking goals directly but rather > depending on Maven's build lifecycle. > Sure... But I want to debug (learn, understand) maven, hence to control the steps. I'll be happy to do that once it won't feel anymore like magic to me. I had run the dependencies first, so I assumed the state is as expected. Wayne Fay wrote > > Read the error message again. > "The packaging for this project did not assign a file to the build > artifact" > > That is why the file attribute was not set. > But I didn't take it away, and it was set in the 2.2 tag case!? And as <code>mvn clean package -DskipTests</code> works, producing my snapshot jars, 'assigning a file to the build artifact' is done dynamically. The static settings in the poms are OK... So, there must be a earlier phase in the lifecycle which is responsible for that? Marc -- View this message in context: http://maven.40175.n5.nabble.com/Fail-to-build-snapshot-tp5713546p5713800.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
