Re: Maven 3 versions of the plugins

2010-05-18 Thread Paul Benedict
evelopers List > Subject: Re: Maven 3 versions of the plugins > > The intention of the warning was to make it pretty clear that you're > running with some risk. We have already agreed that the entire > "parallel" feature is to be marked as "experimental" (altho

RE: Maven 3 versions of the plugins

2010-05-18 Thread Jeff Jensen
List Subject: Re: Maven 3 versions of the plugins The intention of the warning was to make it pretty clear that you're running with some risk. We have already agreed that the entire "parallel" feature is to be marked as "experimental" (although with the explicit adding of @thread

Re: Maven 3 versions of the plugins

2010-05-18 Thread Benjamin Bentmann
Kristian Rosenvold wrote: Isn't the current solution noisy enough ? +1, looks fine to me. ti., 18.05.2010 kl. 13.32 -0500, skrev Paul Benedict: Why would Maven allow parallel builds that are not thread-safe? Simply because the absence of the @threadSafe annotation does not imply that the

Re: Maven 3 versions of the plugins

2010-05-18 Thread Kristian Rosenvold
The intention of the warning was to make it pretty clear that you're running with some risk. We have already agreed that the entire "parallel" feature is to be marked as "experimental" (although with the explicit adding of @threadSafe to the mojos I personally think regular "parallel" is good for p

Re: Maven 3 versions of the plugins

2010-05-18 Thread Paul Benedict
Why would Maven allow parallel builds that are not thread-safe? Granted, it's the developer's choice to take the chance, but I just don't see why it's beneficial to allow builds being potentially corrupted unbeknownst to the builder. 2010/5/17 Arnaud Héritier : > In m3 if you activate the // mode

Re: Maven 3 versions of the plugins

2010-05-17 Thread Arnaud Héritier
In m3 if you activate the // mode and you have a plugin which isn't marked as compatible you'll have a warning like that : [WARNING] * [WARNING] * Your build is requesting parallel execution, but project * [WARNING] * contains t

Re: Maven 3 versions of the plugins

2010-05-17 Thread Paul Benedict
I actually want to recommend something more formal inside of Maven. It seems that some kind of rule should exist to force a minimum version. Paul 2010/5/17 Martin Gainty : > > Hi Paul > > > > would a custom rule work? > http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html > >

RE: Maven 3 versions of the plugins

2010-05-17 Thread Martin Gainty
Hi Paul would a custom rule work? http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html ? Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten S