M2e is compatible with what it generate :P Just remove your project from workspace,delete all your .classpath .project and .settings files and import back your project is as a maven project, and you should be good.
If you use some particular plugins, you may have to install a m2e connector too. On Wed, Feb 12, 2014 at 7:09 AM, Andreas Magnusson < [email protected]> wrote: > Could it be that m2e isn't compatible with faceted projects? If I remember > correctly they behave quite differently from normal Eclipse Java project... > > On 11 feb 2014, at 20:07, Matthew Piggott <[email protected]> wrote: > > *mvn eclipse:eclipse* is incompatible with m2e and iirc disables m2e > integration. > > You should never need to manually add the Maven dependencies library, this > suggests to me something you're doing/using in Eclipse is disabling the > integration. > > > On 11 February 2014 13:59, V. Mark Lehky <[email protected]> wrote: > >> Hello. >> >> I am facing the exact same problem as described here: >> < >> https://stackoverflow.com/questions/4859825/how-to-add-maven-managed-dependencies-library-in-build-path-eclipse >> >. >> However, none of the posted solutions seem to work for me. Been >> Googling all day, but still no go. Maybe something changed in the >> latest Eclipse? >> >> I have "Eclipse IDE for Java Developers", Kepler, Build id: >> 20130919-0819. This comes with M2E version 1.4.0. I only installed the >> latest updates. >> >> 1. Create a new Maven Project. >> 2. Use "maven-archetype-quick". BTW: I get the same problem if I skip >> archetype selection. >> 3. Right-click on the project, Properties > Project Facets > Convert >> to faceted form > add _only_ Java. >> 4. It builds with errors, complaining that JUnit is missing (the >> archetype above created a AppTest.java). Check the pom.xml, the >> dependency is there! >> 5. Right-click on the project, Build Path > Add Libraries > Maven >> Managed Dependencies > Next >> 6. At this point I am presented with "Use Maven Project settings to >> configure Maven dependency resolution". Not sure what that is? But I >> am able to click Finish. >> 7. When I click Finish, nothing happens. I do know for sure that I >> have JUnit in my local M2/repository already. >> 8. Right-click on the project, Maven > Update Project also does nothing. >> >> As per the link above, I can run `mvn eclipse:eclipse` from the >> command line to fix the dependencies in Eclipse, but I have to do this >> for every single added dependency? This does not seem correct? Also, >> some people in that discussion suggested that this may in fact cause >> some other problems, but they did not say what. >> >> I have another project in my Eclipse, that has the "Maven >> Dependencies" library as part of the build path. So the "feature" >> works. Any dependency I add to the pom in _that_ project is >> automagically added to the Eclipse build path under Maven >> Dependencies. Unfortunately somebody gave me this already packaged up. >> >> How do I correctly set this up in Eclipse from scratch? What is the >> obvious thing that I am missing? >> >> TIA for any advice. ML. >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > > > _______________________________________________ > m2e-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/m2e-users > > -- Adrien Rivard
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
