You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/27 18:46:56 UTC
[jira] Commented: (MNG-1119) Allow to use custom pom resolution
strategy
[ http://jira.codehaus.org/browse/MNG-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204195#action_204195 ]
Jason van Zyl commented on MNG-1119:
------------------------------------
Implemented in 3.x as a specific workspace resolver interface which IDE integration can utilize. M2Eclipse is already using this interface.
> Allow to use custom pom resolution strategy
> -------------------------------------------
>
> Key: MNG-1119
> URL: http://jira.codehaus.org/browse/MNG-1119
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Embedding
> Reporter: Eugene Kuleshov
> Fix For: 3.x
>
>
> Currently all dependencies come from MavenEmbedder.readProjectWithDependencies() method that is using passed pom.xml to resolve dependencies from m2 repositories.
> It is possible that some of the dependencies could exist as other Eclipse projects in the same workspace. It would be interesting to hook up Eclipse-specific pom resolver, so it would implement IDE-specific logic to check if there are poms avaialble and if nothing is there use default resolution strategy.
--
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