I'm pretty sure I might be bashed for writing this, but what the heck... ;-)
I do still see some need for the maven-eclipse-plugin. To be perfectly clear, I agree that m2e is by far superior in many ways, not only tech-wise, but also conceptionally. Still, at work we had to migrate from m2e to m-eclipse-p a couple of years ago, which included some minor adaptations to the plugin, and it works like a charm since then (that was back in the days when m2e was far away from version 1.0.0). We have a workspace with about 500 projects and we commit the eclipse metadata for each project to our source repository. Changes in the poms don't happen that often, and if needed that one colleague runs m-eclipse-p to update the metadata and commits everything in one go. The other colleagues do their update, refresh in eclipse, maybe run a batch file to download newly referenced jars to the local repo, and they're done. Eclipse will build quite quickly. I just tried the latest m2e version with our projects and, although it's by far better than it was some years ago, I had to tripple my memory settings and wait 20 minutes for the "update project..." and the following build. That's something I can't sell to my colleagues (many of them don't even have enough RAM for that, sadly enough). So I'm herby volunteering to go ahead and pull out some of the adjustments that I did for my customer and I'd be happy to do a release. If there's a chance to get some PMC votes on such a thing ;-). I'd also include a disclaimer on the site that builds with m2e are in many cases closer to the real maven build, that m2e is much more maintained, that it is discouraged to use m-eclipse-p, and that the maven team strongly suggests using m2e. Something like that. WDYT? Andreas 2015-02-02 14:00 GMT+01:00 Benson Margulies <bimargul...@gmail.com>: > Just to be perfectly clear: > > I am volunteering to include archetype in the herd. > > I have submitted INFRA-9100 to move it to git. > I have assigned http://jira.codehaus.org/browse/ARCHETYPE-471 to myself. > > So no need to send any email announcing its demise. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
