+1 I understand Rotert's problem with this plugin. I would personally move it away from Apache repo in GitHub because I think we should not dedicate our spare time to maintain it. The only problem is who will have rights to commit into it, or let the contributors to push pull requests like it is in Jenkins project as Arno mentioned in ApacheCON.
On Sun, Oct 4, 2015 at 11:18 AM, Robert Scholte <[email protected]> wrote: > Hi, > > during the latest upgrade of the plugin-parent I faced several issues with > the maven-eclipse-plugin. > It will take quite some time to fix these issues, but is it worth > maintaining it here? > Nowadays the Maven support for Eclipse is good and stable. > The maven-eclipse-plugin has a lot of integration tests which should be > rewritten, because it always launches a new Maven fork and it takes ages to > complete. This simply blocks good continuous integration of the plugins. > I know there are still some projects with can't use the Maven Integration > of Eclipse and depend on this plugin, so the sources need to stay available > for users so the can extend it for their own usage. > > I therefor propose that we retire maven-eclipse-plugin for the Apache > Maven project and donate it to the Mojohaus project > > If this vote is successful I will make one final release of the plugin, > making > it clear on the plugin site that it has been retired. After that the > source code > will be moved into the "retired" area in Subversion. > > The process for retiring a plugin is described here: > http://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > > [ ] +1 Yes, it's about time > [ ] -1 No, because... > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers Tibor
