Hmm v-m-p may need patching so... Though if your parent needs version X I cannot see how you can pretend to build with anything less than X hence my belief that it is.
Should be trivial to test though On Wednesday, 12 December 2012, Robert Scholte wrote: > > I've talked about this with Benjamin in the past, and he told me the > prerequisite is NEVER inherited. > So we can't define it in the mojo-parent but have to do it for every > plugin. > > Robert > ------------------------------ > Date: Wed, 12 Dec 2012 11:32:52 +0000 > From: [email protected] <javascript:_e({}, 'cvml', > '[email protected]');> > To: [email protected] <javascript:_e({}, 'cvml', > '[email protected]');> > Subject: Re: [mojo-dev] Adding maven prerequisites version in mojo-parent ? > > For a pure pom. the version should be set to the lowest version of amy > plugins required to build that pom... which is what versions is complaining > about. > > for a pom that has <packaging>maven-plugin</packaging> however, that > version is *also* the minimum version of Maven that the plugin will work > with. > > So in your plugin's pom, if you know that the plugin only works with Maven > 2.2.1 because you are using dependencies that start at 2.2.1, give that > plugin the <prerequitsites> > > For example versions-m-p 1.3 has 2.0.9ish (might be 2.0.6 or 2.0.11) as > min due to some issues with prior versions of the maven apis > v-m-p 2.0 has 2.2.1 as min because when we get as far as 2.2.1 we need > fewer work-arounds > v-m-p 3.0 will have 3.0 as min because it will be using the Maven 3 apis. > > but I am only changing the min required version because of bugs that need > fixes in newer versions of Maven or because I need features in newer > versions of Maven. > > We should endevour to support the lowest version of Maven that has the > features the plugin needs. > > For example, my jszip.org experiments *need* 3.0.4 of Maven for some of > the critical "live-develeopment across the entire reactor" functionality, > so it is forcing 3.0.4 as the minimum... though I spend a good deal of time > trying to battle to keep that minimum at 2.2.1, I eventually had to give up > and use an API that is only present in 3.0 and only working in 3.0.4 > > > On 12 December 2012 11:08, Anders Hammar <[email protected]<javascript:_e({}, > 'cvml', '[email protected]');> > > wrote: > > I believe the idea, in the past at least, has been to not require anything > there is no technicla reason for. So, if the plugin works with 2.0.4 why > force a requirement of 2.2.1? The same with Java version. > > /Anders > > > > On Wed, Dec 12, 2012 at 11:45 AM, Tony Chemit > <[email protected]<javascript:_e({}, 'cvml', '[email protected]');> > > wrote: > > While using the superb versions plugin, it cries on me: > > [WARNING] Project does not define minimum Maven version, default is: 2.0 > [INFO] Plugins require minimum Maven version of: 2.2.1 > [INFO] > [ERROR] Project does not define required minimum version of Maven. > [ERROR] Update the pom.xml to contain > [ERROR] <prerequisites> > [ERROR] <maven>2.2.1</maven> > [ERROR] </prerequisites> > > Is there any reason to not adding it ? > > Perhaps it is time to set it (new released plugins will only works with > maven >= 2.2.1), is that a such problem. > > I could also ask why still stay on jdk 1.4 since 1.5 is no more maintain > by Oracle ? > > WDYT ? > > If nobody is against I will create issues and fix them. > > Tony. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > >
