In fact, my solution does not work at all ... My package is correctly generated with wanted files generated by antrun inside of it, but I believe as I use goal "assembly" instead of "single", the related tar.gz is not attached and so not deployed.
I see the following logs : "[WARNING] Removing: assembly from forked lifecycle, to prevent recursive invocation" So it's not usable, as I want this file to be deployed as it was. Is there any way to achieve the following order of operations in a pom ? : - assembly:directory-single to generate a folder - antrun:run to generate checksums against it - assembly:single to package final tar.gz archive I don't want to achieve this in multiple modules, as it is supposed to keep simple and to become the default for our module archetypes ... But it seems impossible to put something else between two assembly executions. -- View this message in context: http://old.nabble.com/Issue-with-assembly-plugin-executions-and-phase-binding--%28prepare-package%29-tp26607839p26791178.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
