[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_68368 ]
Dimitry Voytenko commented on MNGECLIPSE-59: -------------------------------------------- Hi Eugene, There seems to quite a bit of confusion around this issue now. I just wanted to see if if something can be done to clear things up. I don't know what's the state of applied patches right now, but I believe, Mark J. Sinke patch was very satisfactory. I've had it running on our workstations for a while now. If you need help applying that patch, I can adjust it to the current trunk. I believe, all other optimization requests can be easily applied afterwards. If you other patches were applied (i.e. Kenney Westerhof) please let me know, I'll try to test it over here. > 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, 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
