Question

Right now, I have two Eclipse projects – they both use Maven 2 for all their jar-dependency goodness.

Inside Eclipse, I have project Foo included in project Bar’s build path, so that I can use Foo’s classes from project Bar. This works really well in Eclipse land, but when I try:

mvn compile  

inside Bar’s directory, it fails because Maven doesn’t know about the project-to-project relationship in Eclipse’s build path.

If I were using Ant, I would just use it to do something silly like copy foo.jar into project Bar’s classpath, but as far as I can tell, things are done a lot less hackishly in Maven-land.

I’m wondering if there’s a standard workaround for this type of problem – it seems like it would be fairly common, and I’m just missing something basic about how Maven works.

Answer 1

Maybe you are referencing the other project via Eclipse configure-> build path only. This works as long as you use Eclipse to build your project.

Try running first mvn install in project Bar (in order to put Bar in your Maven repository), and then add the dependency to Foo’s pom.xml.

That should work!.