Um, please pardon my ignorance, but how else would you?
-Chris
On Thu, May 17, 2012 at 4:24 PM, Kristian Rosenvold <
kristian.rosenv...@zenior.no> wrote:
> Assuming, of course, that you use the javadoc annotation...
>
> Kristian
>
> Den 17. mai 2012 kl. 06:52 skrev Chris Graham :
>
> > :-)
> >
>
Assuming, of course, that you use the javadoc annotation...
Kristian
Den 17. mai 2012 kl. 06:52 skrev Chris Graham :
> :-)
>
> Ta much.
>
> -Chris
>
> On Thu, May 17, 2012 at 2:27 PM, Kristian Rosenvold <
> kristian.rosenv...@zenior.no> wrote:
>
>> yes
>>
>> Den 17. mai 2012 kl. 06:18 skrev Chri
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
:-)
Ta much.
-Chris
On Thu, May 17, 2012 at 2:27 PM, Kristian Rosenvold <
kristian.rosenv...@zenior.no> wrote:
> yes
>
> Den 17. mai 2012 kl. 06:18 skrev Chris Graham :
>
> > Hi All.
> >
> > Can we mark a plugin as threadSafe AND still have it work under JRE 1.4
> and
> > Maven 2.0.9?
> >
> > O
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,
yes
Den 17. mai 2012 kl. 06:18 skrev Chris Graham :
> Hi All.
>
> Can we mark a plugin as threadSafe AND still have it work under JRE 1.4 and
> Maven 2.0.9?
>
> Obviously, it's ability to run in parallel mode would require Maven 3.
>
> So, if I mark a plugin as being @threadSafe, will it still be
Hi All.
Can we mark a plugin as threadSafe AND still have it work under JRE 1.4 and
Maven 2.0.9?
Obviously, it's ability to run in parallel mode would require Maven 3.
So, if I mark a plugin as being @threadSafe, will it still be able to be
run under the older JRE's and Maven's?
-Chris
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
Hi,
I can take care of that early next week.
2012/5/16 Robin Pradel :
> Hi,
>
> I'd like to use the new ability of maven-clean-plugin 2.5 to retry a delete
> command (http://jira.codehaus.org/browse/MCLEAN-45) in my projects but the
> snapshot state leads to problems while releasing anything.
>
Hi,
I'd like to use the new ability of maven-clean-plugin 2.5 to retry a delete
command (http://jira.codehaus.org/browse/MCLEAN-45) in my projects but the
snapshot state leads to problems while releasing anything.
Are there any plans to release this version in the near future?
I look forward to
13 matches
Mail list logo
