|
On 21/10/2015 6:06 AM, Julien
Vermillard wrote:
I disable m2e on my eclipse, it's just too buggy for me.
So -1 for me :)
Julien,
When was the last time you tried m2e? I would like to point you to
the recent decision[1] by the Apache Maven project to retire their
own plug-in because "Nowadays the Maven support for Eclipse is good
and stable." (their words)
[1]
http://mail-archives.apache.org/mod_mbox/maven-dev/201510.mbox/%3Cop.x55dxii1kdkhrr%40robertscholte.dynamic.ziggo.nl%3E
Hi,
I have been going through leshan's parent POM and noticed
that we are still configuring the Maven Eclipse Plugin in
there. This propably stems from a time when it was not
that easy to import a maven project into eclipse and thus
needed to create the eclipse project files using this
plugin beforehand. However, times are a-changin' and my
assumption is that most developers are using an eclipse
version >= Luna today and thus can take advantage of
the m2e eclipse plugin doing the job for them. I therefore
think that we should simply remove the maven eclipse
plugin definition from the POM which will also prevent the
additional creation of the M2_REPO environment variable
based additions to the build classpath which is simply not
necessary anymore with modern eclipse versions.
Any objections?
Regards,
Kai
|
