[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_64206 ]
Dimitry Voytenko commented on MNGECLIPSE-59: -------------------------------------------- Hi Mark, Another issue that should also be considered is WebTools support. It, pretty much, has the same issue. I.e. WebTools manages dependencies on its own (on the "J2EE Module Dependencies") and sycnrhonizes them as the project classpath dependencies. If Maven2 was enabled for the project this would yield "duplicate classpath entry" error. > 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
