On Mon, Feb 2, 2015 at 12:42 PM, Karl Heinz Marbaise <[email protected]> wrote: > Hi, > > after some discussions at FOSDEM with Hervé, Kristian and Robert in Brussels > i will summarize some ideas we would like to share here: > > Make a final release of all plugins with minium Maven 2.2.1 (prerequisites) > and Java 1.5 > > The current state of this approach can be watched on the dist-tool [2] page. > > After that we can start making releases of the plugins which have minimum > Maven 3.0 and JDK 6 (I think this will bring many cleanups in code etc.)
I have documented the steps required to update a plugin/shared component to Java 6 here http://maven.apache.org/developers/java6.html > To make this more clear for the users the plugin versions should be bumped > to 3.0....independant from their current version. I think we also need a versioning guide for plugins/components to cover stuff like this. That page could also cover Semver, see separate thread for that. > This approach gives us the possibility to make in case of real bugs bug fix > releases of the older plugins for JDK 5 etc. without confusion JDK 5/JDK6 > etc. > > These are the steps to leave Maven 2 completely behind..Yeah ;-) > > Currently we have two (three) exceptions maven-site-plugin (some kind of > special case), maven-scm-publish-plugin and maven-shade-plugin which already > have the Maven 3 requirement. > > > [1] http://www.mail-archive.com/dev%40maven.apache.org/msg102539.html > [2] > https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html > > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
