Seems a wee bit odd that you have "enforcer:enforce" which handles
maven version and java version, then "enforcer:os" which handles os
stuff. I'd rather have enforcer:require-maven, enforcer:require-
java, enforcer:require-os, *
I'm also not keen on the version range muck... but I guess its more
flexible that the 1.0+ and 1.0* stuff I was using. Still though the
version range specification never really felt natural to me ;-)
--jason
On Mar 19, 2007, at 9:04 PM, Brian E. Fox wrote:
There is a new plugin that I'd like to get some feedback on,
particularly on non-windows os's and the unit tests.
The maven-enforcer-plugin picks up where <prerequisites> leaves off
and
allows control over the maven, jdk and os versions of a build.
This plugin was initially conceived here:
http://www.nabble.com/Control-of-maven-using-prerequisites-
tf3231437s177
.html#a8979318
And here:
http://www.nabble.com/Why-is-prerequisites-not-inherited--
tf3236197s177.
html#a9016296
1.0-alpha-1-SNAPSHOT is deployed and the site is here:
http://maven.apache.org/plugins/maven-enforcer-plugin/ (just
deployed so
give it a little bit to completely update)
If all goes well and no major issues are uncovered, then I think it's
ready for staging and a vote.
Thanks,
Brian
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
