On 4 October 2012 11:12, Jean Seurin 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) >
Or at least make it a Warning not an Error. I actually joined this list because of this, and found the relevant code but could not figure out how to feedback the simple fix. cheers Tim -- Tim Pizey - http://pizey.net/~timp _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
