Re: [m2e-users] M2E plugin : please convince me

[Anders Hammar <anders@xxxxxxxxxx>]

The simple answer, IMHO, is that you want incremental build support.
That's what m2e tries to give you. As Maven and its plugins doesn't
support that, m2e can't delegate it. Forcing a Maven build (even if it
would just be part of the full lifecycle) would give you a very slow
Eclipse environment. That's what we had in m2e 0.x, which was not
really usable when you had a decent number of projects.

Regarding configuring the lifecycle mappings, you an now (m2e 1.2+) do
that outside of the pom if you want.

/Anders

On Thu, Oct 4, 2012 at 12:12 PM, Jean Seurin <jean.eastcode@xxxxxxxxx> wrote:
> I've been using maven for a quiet long time now, and I'm still at a loss
> when trying to understand the philosophy behind M2E.
>
> In my view, Maven config defines the project, the IDE reads it, and that's
> it.
>
> Not the other way around: having errors like "M2E plugin execution not
> covered" just doesn't make sense to me.
> And solving the problem by adding a config snippet to the pom looks even
> more startling!
>
> Since when do you make the project config aware of the tool you use to
> develop??
>
>
> Now that's only my very rough point of view, coming from someone that has
> been using the maven command line and that is used to it.
>
> I'm sure there's a good reason why M2E tries to "integrate the maven
> lifecycle phases into Eclipse" - if I may describe it this way - rather than
> bluntly delegating all tasks to Maven itself (since it owns the project
> config).
>
> Please, please, explain to me what bring M2E over pure Maven delegation,
> you'd make my day (if not my week)
>
> rgds
>
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/m2e-users
>