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 of maintainers for long enough. It fails the apache test of offering reasonable responsiveness on the mailing list, so it needs to go. On Dec 25, 2015 3:38 PM, "Gary Gregory" <[email protected]> wrote: > 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" <[email protected]> wrote: > > > 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 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
