Another means of doing this, is to always build module D as you put it.
But, assuming the distribution is just an application of the assembly
plugin (or it's derivatives in concept), just tie the execution of the
plugin(s) to the DEPLOY phase.
That's exactly how I achieved an upload on my package
I tried that and it did not make any difference (with mvn 3.0.4). The
project is BTM on codehaus if someone wants to try it out.
Thanks,
S.
On Wed, May 16, 2012 at 7:43 PM, Robert Scholte wrote:
> Could you first update to version 2.3 and see if that makes any difference?
>
> -Robert
>
> Op Wed,
Could you first update to version 2.3 and see if that makes any difference?
-Robert
Op Wed, 16 May 2012 19:21:29 +0200 schreef Stephane Nicoll
:
I am not sure, here is the partial log of the dryRun
snicoll@cobra:~/Projects/btm$ mvn -DdryRun=true release:prepare
[INFO] Scanning for projects
I am not sure, here is the partial log of the dryRun
snicoll@cobra:~/Projects/btm$ mvn -DdryRun=true release:prepare
[INFO] Scanning for projects...
[INFO]
[INFO] Reactor Build Order:
[INFO]
[INFO] Bitronix Transaction Manage
Looks like https://jira.codehaus.org/browse/MRELEASE-571
I have an idea how to fix this for Maven3 and if that works it'll be part
of 2.4
-Robert
Op Wed, 16 May 2012 19:05:14 +0200 schreef Stephane Nicoll
:
Hi,
Is it me or it is not possible to add extra modules with the release
plugi
Hi,
Is it me or it is not possible to add extra modules with the release plugin
?
My use case is simple, I have a multi-modules project[1] that builds 3
modules by default (A,B,C) and a "dist" profile adds an extra fourth
project (D). When I release this project, I want to build A,B,C,D at both
s
