| Summary: | Transitive test dependencies on Eclipse classpath | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Harald Wellmann <hwellmann.de> | ||||
| Component: | m2e | Assignee: | Project Inbox <m2e.core-inbox> | ||||
| Status: | CLOSED NOT_ECLIPSE | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | igor | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Harald Wellmann
Please provide complete standalone sample project and steps to reproduce the problem. Created attachment 198183 [details]
Test case
Here is a test case, a parent project with two modules.
Import the project into Eclipse and run test-scope-bug-parent/test-scope-client/src/test/java/com/blogspot/hwellmann/testscope/ClasspathTest.java as JUnit test from Eclipse.
This will print the classpath to System.out.
The output includes .../test-scope-dep/target/test-classes and other dependencies of test-scope-dep.
The problem does not occur when the packaging of test-scope-client is jar (not
war), so this may be an issue of m2eclipse WTP rather than m2e core. I'm using
Maven Integration for WTP (Optional) 0.11.1.20101108-1810
This is a bug in m2e-wtp integration, a separate project hosted at github. This bug appears to have been fixed in recent m2e-wtp builds (see [1]), but I am not familiar with the code enough to tell for sure. [1] http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00692.html PS: FWIW, m2e 1.0.0 generates correct classpath if I change test-scope-client packaging to "jar". |