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

<p>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:</p>

<pre><code>mvn compile 
</code></pre>

<p>inside Bar's directory, it fails because Maven doesn't know about the project-to-project relationship in Eclipse's build path.</p>

<p>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.</p>

<p>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.</p>

I think the best way to handle it is to make Bar a Maven project just like Foo, and then
```
mvn install
```
it so it is available in your local Maven repository. The drawback is that you have to install that project every time you want Maven to see the changes you make to Bar.