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

Drew Farris commented on MNGECLIPSE-59:
---------------------------------------

I've hacked together a solution that seems to work for now and only touches the 
Maven2Plugin class. I've generated the attached patch against version 111 of 
Maven2Plugin and attached it as mngeclipse-59-drew-hack.txt 

The drawback of this solution is that it builds a list of projects in the local 
workspace that could potentially be used to resolve dependencies once, the 
first time resolveClasspathEntries is called. Ideally, I'd somehow hook into 
workspace change events and rebuild the list as necessary, but I really don't 
know the Eclipse API that well. 

Furthermore, it only looks at the group id and an artifact id -- version is 
ignored completely for now.

As I said, this is a hack -- it seems to solve the issue for me -- maybe this 
will be useful to someone else.

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