[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_64136 
] 

Dimitry Voytenko commented on MNGECLIPSE-59:
--------------------------------------------

Hi Mark,

There's another issue with this implementation. It's in the area of PDE 
development and probably is only particular to PDE environment, but this is 
important b/c there's big number of Eclipse plugin developers and that number 
is growing.

The issue is that PDE has its own way of simplifying dependencies and this way 
is essential to the PDE's work. Thus, dependencies information might get 
duplicated (or some of it) in the pom.xml and PDE-s manifest. The same project 
would appear in both "Plugin Dependencies" and "Maven2 Dependencies" classpath 
containers, which triggers build error in Eclipse (duplicated classpath entry).

It seems like the only way to resolve this problem would be to avoid including 
artifacts in the "Maven2 Dependencies" container if they present in other 
containers. Although I don't know how possible this is, I don't know if the 
order in which classpath containers are expanded is known and if there's the 
necessary information to do this.

Thoughts?


> Allow artifact resolution from workspace projects
> -------------------------------------------------
>
>          Key: MNGECLIPSE-59
>          URL: http://jira.codehaus.org/browse/MNGECLIPSE-59
>      Project: Maven 2.x Extension for Eclipse
>         Type: New Feature

>   Components: Dependency Resolver
>     Versions: 0.0.4
>     Reporter: Leonardo Quijano Vincenzi
>     Assignee: Eugene Kuleshov
>      Fix For: 1.0.0
>  Attachments: ArtifactResolver-try3.patch, 
> EclipseArtifactResolver-corrected.patch, EclipseArtifactResolver.patch, 
> maven-embedder-2.1-SNAPSHOT-dep.jar
>
>
> Provide artifact resolution from workspace projects, which override the same 
> artifact from the local or remote repositories. This would allow to work with 
> dependant Eclipse projects without specifying the Eclipse dependency manually.
> The workspace artifact resolution would have to be specified manually, since 
> several Maven-Enabled projects in the same workspace could have the same 
> artifact and version Id. Or at least automatic resolution with an optional 
> override would be nice.
> More comments here:
> http://jira.codehaus.org/browse/MNGECLIPSE-58

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

Reply via email to