You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Milos Kleint (JIRA)" <ji...@codehaus.org> on 2006/04/14 11:29:49 UTC

[jira] Commented: (MNG-1937) Allow to substitute custom artifact resolver

    [ http://jira.codehaus.org/browse/MNG-1937?page=comments#action_63550 ] 

Milos Kleint commented on MNG-1937:
-----------------------------------

Hey, I'm about to integrate this change because it's a better solution than my solution from MNG-1665.
Currently I plan to introduce a MavenEmbedRequest interface that will be passed to the embedder at start() method. That request should replace the various setters, that have actually some meaning only before starting the container. I would like to make the tweaking of the container's components part of the request, rather than the subclassing approach in the current patch.
That means to introduce an interface to pass to the request. The interface will be implemented by the user of the embedder.

 Comments?

> Allow to substitute custom artifact resolver
> --------------------------------------------
>
>          Key: MNG-1937
>          URL: http://jira.codehaus.org/browse/MNG-1937
>      Project: Maven 2
>         Type: New Feature

>   Components: Embedding
>     Versions: 2.0.1
>     Reporter: Eugene Kuleshov
>     Assignee: Jason van Zyl
>     Priority: Critical
>  Attachments: lookupComponents.patch
>
>
> Embedder should allow to substitute custom artifact resolver. The usecase is to be able to use projects that are not deployed to Maven repository but available in IDE (e.g. Eclipse workspace). 
> This would also allow to resolve sources for projects that are not deployed to Maven repository.

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