FYI, I just added require-maven-version too:
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/
tools-maven-plugin/src/main/java/org/apache/geronimo/genesis/plugins/
tools/RequireMavenVersionMojo.java
Since <prerequisites><maven>ver... does not get inherited, can define
this goal to execute on validate to check:
----8<----
<plugin>
<groupId>org.apache.geronimo.genesis.plugins</groupId>
<artifactId>tools-maven-plugin</artifactId>
<executions>
<execution>
<phase>validate</phase>
<goals>
<goal>require-maven-version</goal>
</goals>
<configuration>
<version>2.0.5+</version>
</configuration>
</execution>
</executions>
</plugin>
---->8----
Its a week bit of a hack, but seems to work.
--jason
On Feb 15, 2007, at 8:38 AM, Jason van Zyl wrote:
On 15 Feb 07, at 11:28 AM 15 Feb 07, Brian E. Fox wrote:
Is there any objection to pulling some of that into apache? I took a
look and the syntax makes sense. The only change I might make is
to use
whatever Maven already uses to get the jdk version (if it's not
already
the same)
It can certainly go in the sandbox.
Jason.
-----Original Message-----
From: Jason Dillon [mailto:[EMAIL PROTECTED] On Behalf Of Jason
Dillon
Sent: Wednesday, February 14, 2007 11:17 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites
FYI, docs for that are here:
http://geronimo.apache.org/maven/genesis/plugins/tools-maven-
plugin/usage.html
Was thinking of moving some of that to a plugin in the mojo project
whenever I find some time...
--jason
On Feb 14, 2007, at 8:12 PM, Joakim Erdfelt wrote:
Check out the geronimo tools-maven-plugin Found at
http://svn.apache.org/repos/asf/geronimo/genesis/trunk/plugins/
tools-maven-plugin/
It is used by the current geronimo for enforcing various minimum
aspects of the build environment.
Example: (from
http://svn.apache.org/repos/asf/geronimo/daytrader/trunk/pom.xml )
<plugin>
<groupId>org.apache.geronimo.genesis.plugins</
groupId>
<artifactId>tools-maven-plugin</artifactId>
<executions>
<execution>
<id>validate-java-version</id>
<phase>validate</phase>
<goals>
<goal>require-java-version</goal>
</goals>
<configuration>
<version>1.5*</version>
</configuration>
</execution>
</executions>
</plugin>
Enjoy
- Joakim
Brian E. Fox wrote:
So the initial feature list for the "maven-enforcer-plugin" is:
OS, Maven Rev, Jdk Rev. Anything else that might be usefull from a
Configuration Management standpoint? Most other things can
already be
controlled via pluginManagement/dependencyManagement...although it
doesn't stop someone from overriding at a local pom level.
-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 14, 2007 9:56 PM
To: Maven Developers List
Subject: Re: Control of maven using prerequisites
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: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------
--
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------
-
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For
additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
