Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 0.0.10
-
Fix Version/s: None
-
Component/s: Dependency Resolver
-
Labels:None
-
Environment:Eclipse 3.2, Windows, Maven 2.0.4
-
Number of attachments :
Description
With maven project's test classes and resources are not exposed to the 'outside world'. But with the m2eclipse plugin version 0.0.10 the new "project dependency" feature makes test classes and resources visible to the project that has the dependency.
This results in inconsistent behaviour between the eclipse and the commandline world resulting in projects that compile with eclipse but won't on the command line and jUnit tests that fail within eclipse.
Issue Links
| This issue relates to: | ||||
| MNGECLIPSE-796 | build in eclipse doesn't fail on 'runtime' depency references |
|
|
|
| MNGECLIPSE-296 | Transitive dependencies from parent project computed wrong |
|
|
|
| This issue is related to: | ||||
| MNGECLIPSE-606 | Runtime classpath does not honour workspace dependency classifier |
|
|
|
I think this is one of the issues we will have to live with. As Eclipse does not know a difference between normal execution and test execution (and it's not possible to set different class paths for different source folders AFAIK), it will be your responsibility to make sure that your maven artifacts are up to date.