[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_72573 ] Eugene Kuleshov commented on MNGECLIPSE-59: -------------------------------------------
I pushed some fixes. Namely: changed key in models Map to string (I wonder if it would fix your issue) and fixed issue when artifact version is defined in the parent pom. However there is some weirdness. For instance, when I import maven-tools project from http://svn.apache.org/repos/asf/maven/components/trunk/maven-tools I see some broken dependencies and it looks like maven-core is not being resolved transitively. Not sure if it is anyhow related to the last refactorings or it is just broken snapsht dependencies... > Allow artifact resolution from workspace projects > ------------------------------------------------- > > Key: MNGECLIPSE-59 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-59 > Project: Maven 2.x Extension for Eclipse > Issue Type: New Feature > Components: Dependency Resolver > Affects Versions: 0.0.4 > Reporter: Leonardo Quijano Vincenzi > Attachments: ArtifactResolver-try3.patch, MNGECLIPSE-59, > mngeclipse-59-drew-hack.txt, project-artifacts-2006062701.patch, > project-artifacts-2006062900.patch, project-artifacts.patch > > > 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
