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/03/31 17:09:44 UTC

[jira] Closed: (MNGECLIPSE-97) ignore dependencies in eclipse workspace

     [ http://jira.codehaus.org/browse/MNGECLIPSE-97?page=all ]
     
Eugene Kuleshov closed MNGECLIPSE-97:
-------------------------------------

    Resolution: Duplicate

> ignore dependencies in eclipse workspace
> ----------------------------------------
>
>          Key: MNGECLIPSE-97
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-97
>      Project: Maven 2.x Extension for Eclipse
>         Type: Improvement

>   Components: Dependency Resolver
>     Versions: 0.0.5
>  Environment: eclipse 3.1.2 on linux
>     Reporter: Dan Allen
>     Assignee: Eugene Kuleshov
>  Attachments: MNGECLIPSE-97.txt
>
>
> When a maven project is setup in eclipse, the dependencies between modules are captured as eclipse project dependencies.  However, when m2eclipse gets into the mix, it tries to assign the dependency to the jar file that has been installed in the maven repository.  It makes much more sense for m2eclipse to get out of the way and let eclipse deal with the dependencies if it exists in the workspace.
> This is simply a matter of implementing the following logic:
> 1. scan through dependency artifacts in the pom
> 2. if the dependency has the same groupId (maybe too bold of an assumption?)
>   a. if so, look through all dependent eclipse projects
>   b. find a maven project with the same artifactId and version
>      i. if so, skip this dependency and move to the next

-- 
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