maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Scott Cytacki (JIRA)" <>
Subject [jira] Commented: (MNGECLIPSE-179) Use eclipse artifact resolver for forked maven builds
Date Wed, 16 Aug 2006 15:00:48 GMT
    [ ] 
Scott Cytacki commented on MNGECLIPSE-179:

That use case definately trumps any complications in the local repository.  

One part of the solution could be to have the MavenModelManager marshall its map of eclipse
projects and then unmarshaled them in the forked process.   

I believe that artifact resolvers can be added to the plexus container, and then the forked
maven build will use them.  But I don't know how this done.

> Use eclipse artifact resolver for forked maven builds
> -----------------------------------------------------
>                 Key: MNGECLIPSE-179
>                 URL:
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: New Feature
>            Reporter: Scott Cytacki
>         Assigned To: Eugene Kuleshov
>            Priority: Minor
> We should examine if the eclipse artifact resolver, which was created to address this
issue: MNGECLIPSE-59
> Should be used in forked maven builds.   This would mean that artifacts would not need
to be installed into the local repository, before they could be used by forked maven builds.
> Doing this though, might have some complicated consequences.   For example it might be
possible to install a project without installing a dependency.  How does the reactor handle
this: if sub project A depends on subproject B can A be installed without installing B?
> That seems like a good way to think of this: the Eclipse workspace is like a parent project
that has sub projects one for each eclipse project.  Just like in a traditional multi-project,
 those sub projects can reference dependencies that are not installed.

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