Setting the prerequisites in the parent won't work since these are not 
inherited.
In conclusion there's nothing we can or should change in the parent related to 
the maven version.
FYI: once the next plugin-tools are released, I'll call for a vote for a new  
mojo-parent. Some plugins have critical fixes, like the m-plugin-p and the 
m-site-p. If there are more things which need to be updated, have a look right 
now.
 
-Robert
 


Date: Mon, 7 Feb 2011 19:44:37 +0100
From: [email protected]
To: [email protected]
Subject: Re: [mojo-dev] mojo-parent requires maven 2.0.6 but it does not work...

I don't agree.
The maven prerequisite in a plugin states the minimum version of Maven required 
to use the plugin. What we talk about here is the minimum version of Maven 
required to build the plugin, which is the area for the enforcer plugin.
However, in this case I don't really see the need to updated the enforcer rule 
(or add a new one). IMO the Maven message that 2.0.9 is required by the 
compiler plugin is very clear. The reason for the existing enforcer rule in 
mojo-parent (actually inherited from codehaus-parent), verifying the Maven 
version, is because "Maven 2.1.0 and 2.2.0 produce incorrect GPG signatures and 
checksums respectively.".

/Anders


On Mon, Feb 7, 2011 at 13:36, Mark Struberg <[email protected]> wrote:

imo updating the prerequisite to 2.0.9 in the mojo-parent is the way to go.

LieGrue,
strub

--- On Sun, 2/6/11, Anders Hammar <[email protected]> wrote:

From: Anders Hammar <[email protected]>
Subject: Re: [mojo-dev] mojo-parent requires maven 2.0.6 but it does not work...
To: [email protected]
Date: Sunday, February 6, 2011, 9:57 AM




I believe the enforcer rule is there to prevent the usage of Maven versions 
that has known issues, like when doing releases (pgp issue for example).
I don't see a need to try to keep the enforcer rule updated with the maven 
version required for all used/declared plugins. As you see you get a pretty 
good error message from Maven for that.


/Anders

On Sun, Feb 6, 2011 at 09:41, chemit <[email protected]> wrote:

On Sun, 06 Feb 2011 09:21:37 +0100

Dennis Lundberg <[email protected]> wrote:



> If you look closely at the error message, you will see that it is

> Maven Compiler Plugin that insists on Maven 2.0.9. This is because

> Maven Compiler Plugin 2.3.2 (which is defined in mojo-parent 27) has a

> prerequisite on Maven 2.0.9.



Yes but finally can not use maven 2.0.6 with mojo-parent-27 ?

Should we do something about it (Hope I am not wrong ?).







--

Tony Chemit

--------------------

tél: +33 (0) 2 40 50 29 28

email: [email protected]

http://www.codelutin.com



---------------------------------------------------------------------

To unsubscribe from this list, please visit:



    http://xircles.codehaus.org/manage_email












---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



                                          

Reply via email to