Community
Participate
Working Groups
I have projects A, B, C, D open in the workspace. A has maven dependency on B and C. I configured a junit launch A.envTest with the, project A in classpath. However when I launch junit A.envTest, its running classpath includes A/target/classes and B/target/classes. That is not good because projects A and B sources which are different versions of the maven dependency artefacts, contaminates the runtime. They are also default properties files in the Projects A and B sources which I deliberately cannot be included in the maven artefact. Please allow choice not including other open projects from the workspace in a launch.
Note, that m2e tries to resolve the "maven dependencies" container for the runtime class path the same way maven does. Have you tried removing it in the launch configuration and replacing it by direct dependencies? Otherwise, can you please provide an example project?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
