>> >> Maybe i'm missing something here but maven-eclipse-plugin covers only src >> and basic dependencies - the rest (i.e. gwt, wtp, jsf, cdi, guide etc. >> integration won't be configured via this). >> Using the configurators available from m2e makes a much better >> maven-eclipse-plugin imo and they effectively end up with the same - an >> eclipse configured based on as much it can from the pom.xml. >> >> Or is there some other magic that happens that i'm missing ? >> > > The generation of support for these is hit and miss, just like it is with the > connectors right now. The most supported option is WTP, which is has been in > the m-e-p plugin from day one.
Unless it got a massive update then the WTP support in m-e-p stopped being useful around Eclipse 3.4. Hence why importing with m2e today and disabling it afterwards would be a better approach in my world. /max http://about.me/maxandersen _______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
