Well, synchronized suggests a two way process. This is not what m2e does, it cannot update your pom based on changes you make in the project properties in eclipse.
On Thu, Oct 4, 2012 at 6:09 PM, Jeff <predato...@gmail.com> wrote: > Is it also fair to say that m2e is the bridge between a Maven project > (POM) and the Eclipse project settings? Since Eclipse doesn't have native > support for Maven, m2e converts the POM to an Eclipse project and then > attempts to keep them synchronized through the build/test/deploy/debug > lifecycle via all of the plugins and connectors, which is why it seems to > be an overly complex thing to get configured and working correctly. > > Is that an accurate assessment? > > On Thu, Oct 4, 2012 at 9:49 AM, Andrew Eisenberg <and...@eisenberg.as>wrote: > >> M2e 1.2 now supports placing your lifecycle mapping metadata in a >> global location so that it doesn't need to pollute individual project >> poms. This at least addresses one of your original concerns. To do >> this, there is now a second quickfix in your pom editor to handle >> lifecycle mapping metadata mismatches. >> >> On Thu, Oct 4, 2012 at 4:02 AM, Jean Seurin <jean.eastc...@gmail.com> >> wrote: >> > I'm surprised doing an easy `mvn install` on each every component >> manually >> > is not considered 'incremental build' by the community … >> > >> > :) ok, just joking >> > >> > thanks for that brief and enlightening comment. >> > >> > I get it now, and I think M2E is worth a new configuration attempt to >> get >> > that legendary 'incremental build support' -- and an update to 1.2.x , >> big >> > thanks for this tip >> > >> > That said, we've had that many discrepancies in the past between M2E vs >> CLI >> > that I've had to advise people using M2E in my team to do CLI for every >> > goal, defeating the purpose of M2E and indeed the usage of Eclipse >> itself >> > because there doesn't seem to be any alternative to M2E for Maven >> support >> > (might be wrong here) . >> > >> > Anyway, laudable goal, the discrepancies should disappear as the project >> > matures over time. >> > >> > Looking forward to try the maven incrermental build solution! >> > >> > cheers >> > >> > >> > On Thu, Oct 4, 2012 at 6:44 PM, Anders Hammar <and...@hammar.net> >> wrote: >> >> >> >> 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.eastc...@gmail.com> >> >> 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@eclipse.org >> >> > https://dev.eclipse.org/mailman/listinfo/m2e-users >> >> > >> >> _______________________________________________ >> >> m2e-users mailing list >> >> m2e-users@eclipse.org >> >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > >> > >> > >> > _______________________________________________ >> > m2e-users mailing list >> > m2e-users@eclipse.org >> > https://dev.eclipse.org/mailman/listinfo/m2e-users >> > >> _______________________________________________ >> m2e-users mailing list >> m2e-users@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > > > > -- > Jeff Vincent > predato...@gmail.com > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! > > > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/m2e-users > > -- Fotografie http://schutte.name/
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
