Hello maven users
We are using the maven assembly plugin to copy all generated modules and
dependencies to one "central" folder. For this we created a dedicated
child module that used the assembly plugin as desribed in the FAQ
(http://maven.apache.org/plugins/maven-assembly-plugin/faq.html#mod
Could'nt you use a profile for that purpose?
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Cheers,
Guillaume
Le 27/06/2011 16:23, Jean-Pierre Bergamin a écrit :
Hello maven users
We are using the maven assembly plugin to copy all generated modules
and dependencies
Good point, thanks. I tried to only add the distribution child module
for a given profile like this:
dist
distribution_project
So the assembly plugin is only run when setting the dist profile like:
mvn
From what I undesrtand of Maven (I am not completely new but I never
read the code and other insights of it), when you call mvn some-goal on
a multi-module project, it is equivalent to calling this goal on every
module of the project (in the reactor order of course). Hence, when you
call assemb
No, you shouldn't be doing that in the parent project. As the parent project
needs to be built before the children, it will not work (or will require
some workaround). The profile you have is what I would suggest. Or, maybe
even keep this module outside of the build all together as a separate
proje
Actually, I would simply have added the profile in the child module and
activate it through some system property on the command-line:
mvn -Dbuild.dist=true package
dist
build.dist
maven-assembly-plugin
2.2.1
jar-with-dependencies
make-assembly
package
single
Guillaume
Thank you. The activation with a property is even more comfortable.
Best regards
James
Am 28.06.2011 08:23, schrieb Guillaume Polet:
Actually, I would simply have added the profile in the child module and
activate it through some system property on the command-line:
mvn -Dbuild.dist=true packa
