[ http://jira.codehaus.org/browse/MNGECLIPSE-194?page=all ]
Eugene Kuleshov closed MNGECLIPSE-194.
--------------------------------------
Resolution: Duplicate
This is covered by MNGECLIPSE-59. So, if avaialable, Maven dependencies will be
resolved from the Wrokspace.
> Adding a M2 Eclipse project to another M2 Eclipse project overwrites Maven 2
> Dependencies
> ------------------------------------------------------------------------------------------
>
> Key: MNGECLIPSE-194
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-194
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
> Affects Versions: 0.0.9
> Environment: Eclipse 3.2 running on Windows XP under Java 1.4.2_09
> Reporter: Eric
> Attachments: untitled.bmp
>
>
> I have to M2 enabled Eclipse projects, a & b. b's build path has a project
> reference to a. Both will have accurate Maven 2 Dependencies. However if I
> create a run or debug configuration I see that a Maven 2 Dependencies is on
> the classpath. When I run the application and examine the -classpath
> generated by Eclipse, it become obvious that the Maven 2 Dependencies
> contents are the dependencies only of project a, not a combination of a & b
> as I would expect.
> Please help! The only way I know of to use code swap in Eclipse debugging is
> if I have all the dependent project I want to hot-edit on the build path as
> project references. However right now that messes up the whole classpath.
> Thanks!
--
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
