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]> 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 > > >
