Ok that's right. The prerequisite is intended for tools and isn't inherited (making it not good for normal builds) but does apply at runtime. In this instance, the prerequisite is the most appropriate way to require the maven version.
-----Original Message----- From: Richard van Nieuwenhoven [mailto:[EMAIL PROTECTED] Sent: Thursday, April 03, 2008 6:08 AM To: Maven Developers List Subject: Re: [VOTE] Release Maven Eclipse plugin version 2.5.1 Hi, the requireMavenVersion also applies to the runtime, but 2.0.8 is just required for the testing during the build. As far as i know not for the runtime. We use the plugin in a lot of projects that are locked to maven 2.0.7. So please limit it only for the build time. regards, Ritchie Jerome Lacoste wrote: > On Wed, Apr 2, 2008 at 11:13 AM, Arnaud HERITIER <[EMAIL PROTECTED]> wrote: >> Hi Jerome, >> >> As you noticed, this plugin requires to be build with maven >= 2.0.8 >> because of some tests with encodings. >> I'll add an enforcer rule as Benjamin proposed. > > I had added a patch to the issue hat uses the inbbuild POM > requireMavenVersion instead of using the enforcer plugin. That worked > for me. > > Cheers, > > Jerome > > --------------------------------------------------------------------- > 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]
