Maven dependency is not found when that dependency is open in a project in the same workspace

Vote count: 0

The title was a bit difficult to form given the issue. Here is a better explanation.

I have 2 projects in an Eclipse workspace, Project A and Project B.

Project A is a maven project that compiles to a jar and I typically run a maven install to deploy it to my local m2 repository.

Project B is also a maven project but is a web application and uses Project A as a dependency. It uses this snippet from the pom to add Project A as a dependency:

    <dependency>
        <groupId>com.sample</groupId>
        <artifactId>sample-consumer</artifactId>
        <version>${sample.version}</version>
    </dependency>

When Project A is OPEN and I run Project B, anytime it tries to reference something from project A it throws a file not found exception.

When Project A is CLOSED and deployed to my maven repo the references from Project B to Project A work as they should.

This is an incredible hassle when I need to make constant changes to Project A. Does anyone have a way to fix this? I've had a scenario like this in the passed run smooth but am not sure of the trick.

If you need to see something more please ask.

asked 40 secs ago

nmb1106

This entry passed through the Full-Text RSS service - if this is your content and you're reading it on someone else's site, please read the FAQ at http://ift.tt/jcXqJW.

Maven dependency is not found when that dependency is open in a project in the same workspace