You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Eugene Kuleshov (JIRA)" <ji...@codehaus.org> on 2006/12/10 20:35:41 UTC
[jira] Commented: (MNGECLIPSE-216) JAR wrongly inserted into
classpath
[ http://jira.codehaus.org/browse/MNGECLIPSE-216?page=comments#action_82301 ]
Eugene Kuleshov commented on MNGECLIPSE-216:
--------------------------------------------
Please attach example Eclipse project(s) with required maven poms that will be enough to reproduce this issue. Thanks.
> JAR wrongly inserted into classpath
> -----------------------------------
>
> Key: MNGECLIPSE-216
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-216
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Components: Dependency Resolver
> Affects Versions: 0.0.9
> Environment: Eclipse 3.2, Mac OS X
> Reporter: Matthias Bohlen
> Attachments: EclipseSnapshot.pdf
>
>
> My project consists of several subprojects. When I enable the Maven 2 integration plugin, it creates a Maven2 Dependencies node on the build path. This node contains all the foreign JARs I use but it also contains three of my own JARs (although my project builds about 20 subprojects).
> Now, the problem is that Eclipse compiles and runs the unit tests against those three JARs in my local repo, not against the source code in my work-area.
> I do not understand what is so special about those three subproject JARs and why the Maven 2 plugin does this at all. What can I do to remove those three wrong entries on the Dependencies node?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira