maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From fhomasp <>
Subject Re: Create complicated client jar release target(s)
Date Tue, 07 Dec 2010 13:19:45 GMT

In the local repository?  I guess they'll get over it :-)

I think I'm going to exclude the release modules from the module list, and
include them in a seperate profile like this:


Because there already is a parent pom, which is used to build the
applications in development rather frequently.  If I add the release modules
to the standard module list they will always get included in the build
process.  It's better that no one sees any release being mentioned unless
they invoke a build with release profile on.

If any of my reasoning is flawed, by all means, point it out :-)

Antonio Petrelli wrote:
> 2010/12/7 Antonio Petrelli <>:
>> 2010/12/7 fhomasp <>:
>>> Ok, but that would mean that the extra release modules are built
>>> whenever a
>>> mvn package or clean or ... command is invoked on the parent pom.  I'm
>>> quite
>>> sure that they won't like that.
>> If you don't bind the "assembly:single" goal to the package phase, it
>> won't be built in package phase.
> Just forgot that, anyway, when you install the assembly module, it is
> still a POM-packaged Maven project, and it will be installed in the
> local repository, but I don't think it is much a problem, right? :-D
> Antonio
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

View this message in context:
Sent from the Maven - Users mailing list archive at

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message