[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_66846 ]
Drew Farris commented on MNGECLIPSE-59: --------------------------------------- Dimitry, It's an attempt to get the eclipse plugin to resolve artifact dependencies by looking at workspace projects instead of looking for artifacts (jars) in the local repository. It does this by cataloging the projects in the local workspace that are maven projects. In the resolveClasspathEntries() method, it checks these for group and artifact id's that match the artifact that is being searched for. If found, it adds a project reference to the Maven2 Dependencies library instead of a jar reference. > 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 > Attachments: ArtifactResolver-try3.patch, MNGECLIPSE-59, > mngeclipse-59-drew-hack.txt > > > 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
