You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brian E. Fox" <br...@reply.infinity.nu> on 2007/02/15 02:42:27 UTC

Control of maven using prerequisites

Now that 2.0.5 is out and more frequent releases are expected, I think
that http://jira.codehaus.org/browse/MNG-2423 is even more important.
Currently the prerequisites value is not inherited and thus we can't use
it in a company "super-pom" to enforce a minimum Maven version. My
workaround is to create an empty plugin that has a prereq and include
that in the super-pom. This seems kludgey an kind of unnecessary since
there is a field in the pom to do this...it just only applies if defined
in each child pom or when building from a reactor that contains it. Is
there any chance this can get bumped to 2.0.6? I'm willing to try and
submit a patch I could get a pointer where to look.

 

Thanks,

Brian


Re: Control of maven using prerequisites

Posted by Jason van Zyl <ja...@maven.org>.
On 14 Feb 07, at 8:42 PM 14 Feb 07, Brian E. Fox wrote:

> Now that 2.0.5 is out and more frequent releases are expected, I think
> that http://jira.codehaus.org/browse/MNG-2423 is even more important.
> Currently the prerequisites value is not inherited and thus we  
> can't use
> it in a company "super-pom" to enforce a minimum Maven version. My
> workaround is to create an empty plugin that has a prereq and include
> that in the super-pom. This seems kludgey an kind of unnecessary since
> there is a field in the pom to do this...it just only applies if  
> defined
> in each child pom or when building from a reactor that contains it. Is
> there any chance this can get bumped to 2.0.6? I'm willing to try and
> submit a patch I could get a pointer where to look.
>

The prereq is specifically for plugins, or other tools, that need a  
specific version of Maven. It was not meant as a means of enforcement  
for your development environment. Trying to mix these concerns would  
cause problems.

I think what you need is a plugin that runs in the validate phase  
(call it the Enforcer Plugins :-) that checks things like jdk  
version, mvn version, operating system or whatever else you might  
want. Configure this in your parent POM and then you're all set.

Jason.

>
>
> Thanks,
>
> Brian
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org