I strongly second that the maven-eclipse-plugin be retired. For us working in Eclipse, the m2e integration is the way to go. Also, there has not been any active work on that plugin for many years and I think we should clearly indicate to the community that there is very little hope anyone would fix any issues that people (still) using m-eclipse-p run into.
However, I don't think that the maven-archetype-plugin should be retired. Although there might not be very much work on it, it is used in many Get Started guides on the Internet. /Anders On Mon, Feb 2, 2015 at 10:23 AM, Michael Osipov <1983-01...@gmx.net> wrote: > Hi folks, > > I have performed another cleanup on JIRA in the last couple of days, most > of on old issues. > Right now, we have more than 2000 open issues. Not manageble from my point > of view. > > I have noticed that several plugins haven't been touched in years. What is > the status of > the following plugins: > > http://maven.apache.org/plugins/maven-docck-plugin/ > http://maven.apache.org/plugins/maven-doap-plugin/ > http://maven.apache.org/plugins/maven-repository-plugin/ > http://maven.apache.org/plugins/maven-stage-plugin/ > http://maven.apache.org/plugins/maven-eclipse-plugin/ > http://maven.apache.org/plugins/maven-verifier-plugin/ > http://maven.apache.org/plugins/maven-patch-plugin/ > http://maven.apache.org/plugins/maven-pdf-plugin/ > http://maven.apache.org/archetype/maven-archetype-plugin/ > > Is anyone working on them or planning to release a version? Any thoughts > or objections? > > I'd like to retire them and clean up JIRA plugin by plugin. > > Michael > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
