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

Yuri Schimke commented on MNGECLIPSE-59:
----------------------------------------

The patch fixes a number of issues that I had reported in MNGECLIPSE-147, 
however it does not seem to find resources, only the actual classes.

System.out.println(XXX.class); 
   interface xxx.XXX

System.out.println(XXX.class.getResource("/META-INF/applicationContext.xml")); -
   null

System.out.println(new ClassPathResource("/META-INF/applicationContext.xml", 
XXX.class).exists());
   false


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

Reply via email to