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
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
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
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
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
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
la copie de ceci est interdite. Ce message
> sert à l'information seulement et n'aura pas n'importe quel effet légalement
> obligatoire. Étant donné que les email peuvent facilement être sujets à la
> manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu
fourni.
> Date: Mon, 17 May 2010 16:42:49 -0500
> Subject: Maven 3 versions of the plugins
> From: pbened...@apache.org
> To: dev@maven.apache.org
>
> Lots of plugins are up for vote to be @threadSafe with Maven 3. Does
> Maven 3 have any mechanism to reject plugins prio
Lots of plugins are up for vote to be @threadSafe with Maven 3. Does
Maven 3 have any mechanism to reject plugins prior to the versions
being released? What happens if someone uses a Maven 2 version?
Paul
-
To unsubscribe, e-mail
