[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[m2e-users] Mixing classpaths between projects?
|
Hi!
In Eclipse Helios SR-2 (see below) with Maven Integration 0.12.1 (ditto)
I noticed this strange behavior:
With several maven projects in Eclipse,
I used (referenced) a java class in a Java file and Eclipse did not complain.
command line maven complained.
It turned out, that class was in a dependency of project B, while I
coded in project A.
Project A did not have the required dependeny declared in pom.xml.
That is why maven in command line failed.
But in Eclipse, pressing F3 on the reference in the file in project A
opens the definition file in the Maven dependencies of project B.
Why does it include the classpath of project B for project A?
In project A properties, the Build Path has no references to project B.
Am I overlooking something?
Version info:
Eclipse Java EE IDE for Web Developers.
Version: Helios Service Release 2
Build id: 20110301-1815
Maven Integration for Eclipse (Required) 0.12.1.20110112-1712 org.maven.ide.eclipse.feature.feature.group
Regards,
David Balažic
