[
https://jira.codehaus.org/browse/MNG-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-1119:
--------------------------------
Fix Version/s: (was: Issues to be reviewed for 3.x)
3.0
> Allow to use custom pom resolution strategy
> -------------------------------------------
>
> Key: MNG-1119
> URL: https://jira.codehaus.org/browse/MNG-1119
> Project: Maven
> Issue Type: Improvement
> Components: Embedding
> Reporter: Eugene Kuleshov
> Fix For: 3.0
>
>
> 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 was sent by Atlassian JIRA
(v6.1.6#6162)
