maven-issues mailing list archives

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

Dimitry, some testing would be great.

Regarding the duplicate project dependencies.  I would expect the JDT to handle this, I'd
be curious how this is handled by the eclipse plugin classpath container.

On the second point, I agree, A should update as soon as B's pom is saved.  Since m2eclipse
is already listening to pom changes this should be straight forward.  To optimize, each maven
eclipse project can listen to all of its dependencies which are maven eclipse projects.  We
might need a new event for this, but hopefully there is an existing event we can use.

Performance is something that needs to be tested.  There is a lot of room for improvement,
but I didn't want to do it without reason.

> 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