Re: What happened to Maven Eclipse Plugin?

2015-12-27 Thread Baptiste Mathus
+1. Using M2E almost daily (i.e. when doing Java programming). M2E has been improving a lot since its beginning. And has been stable for us for many years already. The biggest issue at that time was actually generally not M2E itself, but the M2E-WTP /bridge/ which was indeed way more unstable

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Robert Scholte
Hi Michael, it was half forgotten, half intended. My original idea was to donate it to MojoHaus and once they made there first release we could do final release here and refer to the the maintainers. However, MojoHaus hasn't found someone to maintain it over there. Other argument: sources

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Robert Scholte
Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov : Robert, just read the discussion on mojohaus-dev. Does this actually mean that you need to respin to vote for complete retirement? I would do so. I don't see a reason for a respin of the vote: we decided to

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Michael Osipov
Robert, just read the discussion on mojohaus-dev. Does this actually mean that you need to respin to vote for complete retirement? I would do so. I would continue as instructed by our retirement plan, issue, final release with notice. Moreover, I would add warning log output to every mojo

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Michael Osipov
Am 2015-12-25 um 14:25 schrieb Robert Scholte: Op Fri, 25 Dec 2015 13:09:26 +0100 schreef Michael Osipov [...] I would continue as instructed by our retirement plan, issue, final release with notice. Moreover, I would add warning log output to every mojo that this plugin has been retired.

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Benson Margulies
On Fri, Dec 25, 2015 at 4:22 PM, Gary Gregory wrote: > Yeah, I've avoid m2e until the other day to see if it got any better. Not. > So your solution is to switch IDEs... hm, not a huge fan of IJ... is there > an Eclipse-like Java Perspective? I find file based editing

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Jeff Jensen
> > Do those of you who are Eclipse users find m2e adequate? I've successfully used m2e for many years on many different systems (different customers). I suggest asking about any issues on the m2e users list. On Fri, Dec 25, 2015 at 2:37 PM, Gary Gregory wrote: > I'm

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Gary Gregory
Yeah, I've avoid m2e until the other day to see if it got any better. Not. So your solution is to switch IDEs... hm, not a huge fan of IJ... is there an Eclipse-like Java Perspective? I find file based editing retarded. Gary On Dec 25, 2015 12:49 PM, "Benson Margulies"

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Robert Scholte
Op Fri, 25 Dec 2015 21:37:55 +0100 schreef Gary Gregory : I'm still surprised that no one wants to maintain this. Do those of you who are Eclipse users find m2e adequate? I don't. Unless I do not know how to set it up. For example, importing the log4j2 projects

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Gary Gregory
I'm still surprised that no one wants to maintain this. Do those of you who are Eclipse users find m2e adequate? I don't. Unless I do not know how to set it up. For example, importing the log4j2 projects creates some projects with errors. Gary On Dec 24, 2015 2:44 PM, "Michael Osipov"

Re: What happened to Maven Eclipse Plugin?

2015-12-25 Thread Benson Margulies
Eclipse's single classpath makes it fundamentally broken with any maven project that has test dependences. So some of us bailed to intellij long ago. m-e-p has one set of incurable issues, and m2e, while much improved, can still eat all your memory on a moderate project. We've watched the lack

What happened to Maven Eclipse Plugin?

2015-12-24 Thread Michael Osipov
Hi Robert, back in October the result of the retirement vote [1] was positive. The plugin is still online without notice, issues are still open in JIRA and no repo is at GitHub. Did you simply forget that? Michael [1] https://www.mail-archive.com/dev%40maven.apache.org/msg107104.html