The Maven Eclipse Plugin Team advice to use m2e now, but as it's
said on its main
page :
"... there are project setups and workflows that still work more
efficiently with statically generated Eclipse metadata - for
example when there is a large number of projects in a reactor.
That's where the Maven Eclipse Plugin can still help you."
We currently don't push in our code repository the eclipse files,
this allow developers to choose which IDE they want to use to
develop Leshan.
The maven eclipse plugin allow us to add specific eclipse
configuration to projects (like a formatter at project level).
Users could still use m2e but they need to some configuration by
hands (like adding formatter, code template ...)
The perfect solution would be to have the possibility to do a mvn
eclipse:eclipse or a mvn eclipse:m2e (that was able with old
version of MavenEclipsePlugin ... I don't know why they remove
it)
Simon
Le 22/10/2015 09:28, Julien Vermillard
a écrit :
I have a 200 module project at work. M2E tends to be
slower and buggy than mvn eclipse:eclipse
(clean/refresh/update/pray/reboot-eclipse cycle for trying
to solve random errors).
I'm using mars.1.
Julien
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 :)
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
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
_______________________________________________
leshan-dev mailing list
leshan-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/leshan-dev
|
