In Eclipse m2e, how to reference workspace project?

java eclipse maven m2e
Wudong picture Wudong · May 21, 2012 · Viewed 36.9k times · Source

How can I reference another workspace project using Eclipse m2e?

Do I have to add a project dependency in the project setting? But in that case the dependency is not shown in the pom.

If I set them in the pom, it will not reference the project in workspace but reference the jar in the local repository. Quite annoying, anyone can help?

Answer

nwinkler picture nwinkler · May 22, 2012

The correct way to do this is the following:

  • Use the dependencies section in the POM file exclusively, don't fiddle with the Eclipse project references. Right-click the project, then select Maven > Update Project Configuration to reset the project to the Maven default settings. This way, m2e has ownership of the dependencies.
  • Make sure all referenced projects are open in Eclipse and have the Maven nature enabled.
  • Check the Maven settings for each project, make sure that groupId, artifactId and version match with the projects you have open in Eclipse. So if the project you depend on has version 1.0.0-SNAPSHOT in Eclipse, make sure that the depending project's POM file references version 1.0.0-SNAPSHOT in the dependencies section.
  • Enable Workspace Resolution for each of the projects. Right-click the project, then Maven > Enable Workspace Resolution.
  • Finally, if the projects are still not resolved, right-click the project again, then Maven > Update Project

This should solve your problem. If after this, your dependencies are still referenced from the file system, check the groupId, artifactId and especially version of each dependency again.

Also check if you don't have any errors in your project - try to run Maven install.

Related questions

How to add pom.xml to existing Eclipse project?

I'm new to Maven and use Eclipse Juno. I've installed Maven Integration for Eclipse. There are three options in File > New > Other > Maven: 1. Checkout Maven Projects from SCM2. Maven Module3. Maven Project But I don't see Maven2 …

Read More
get rid of POM not found warning for org.eclipse.m2e:lifecycle-mapping

With intent to get m2e 1.0 working correctly I have had to specify the lifecycle mapping: <pluginManagement> <plugins> <plugin> <groupId>org.eclipse.m2e</groupId> <artifactId>lifecycle-mapping</…

Read More
Maven and eclipse: a reliable way to add non-Maven or external jars to a project?

Maven is great. It mostly keeps me out of jar dependency hell by specifying versions of dependent packages in the pom configuration, and applies them automatically. It also has great integration with Eclipse via m2e, so that things work …

Read More