maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Elliot (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects
Date Wed, 16 Aug 2006 06:18:54 GMT
    [ ] 
Robert Elliot commented on MNGECLIPSE-59:

I applied the patch to a clean check out from Trunk last night, built and upgraded to the
0.0.10 plugin.  It appears to work fine in terms of doing what it's meant to; however, I had
dual entries in the classpath of many of my projects because I had previously put the project
in the POM and added it as a project in the Eclipse classpath.  Particularly in the case of
a WTP project that made the whole workspace unstable - in fact the only way I was able to
remove the duplicate entries from the WTP project was to close the workspace, go into the
.settings folder via Windows Explorer and remove the WTP dependencies manually.  Which makes
me wonder if having a dual entry on the classpath results in some kind of infinite loop? 
I'm fairly sure that vanilla Eclipse lets you recover errors like that without needing to
alter files in notepad.

> Allow artifact resolution from workspace projects
> -------------------------------------------------
>                 Key: MNGECLIPSE-59
>                 URL:
>             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:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message