maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brad Davis (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects
Date Fri, 24 Mar 2006 01:01:11 GMT
    [ ] 

Brad Davis commented on MNGECLIPSE-59:

The patch appears to be missing the EclipseMavenEmbedder referenced in one file.  In addition
if you have a project that is closed in your workspace, ALL the artifact resolution will fail.
 This is because Maven2Plugin.getWorkspaceNature(...) does not test if a project is open before
trying to get its nature.  this can be fixed by adding a project.isOpen() call and automatically
continueing the for loop if its false.  

> Allow artifact resolution from workspace projects
> -------------------------------------------------
>          Key: MNGECLIPSE-59
>          URL:
>      Project: Maven 2.x Extension for Eclipse
>         Type: New Feature

>   Components: Dependency Resolver
>     Versions: 0.0.4
>     Reporter: Leonardo Quijano Vincenzi
>     Assignee: Eugene Kuleshov
>      Fix For: 1.0.0
>  Attachments: EclipseArtifactResolver-corrected.patch, EclipseArtifactResolver.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