[
https://issues.apache.org/jira/browse/MSHARED-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305614#comment-15305614
]
ASF GitHub Bot commented on MSHARED-336:
----------------------------------------
Github user pono closed the pull request at:
https://github.com/apache/maven-shared/pull/6
> Create a method in the DependencyGraphBuilder that accepts the reactor
> projects to collect unbuilt dependencies
> ---------------------------------------------------------------------------------------------------------------
>
> Key: MSHARED-336
> URL: https://issues.apache.org/jira/browse/MSHARED-336
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-dependency-tree
> Reporter: Jason van Zyl
> Assignee: Hervé Boutemy
> Fix For: maven-dependency-tree-2.2
>
>
> https://github.com/apache/maven-shared/pull/5
> https://github.com/apache/maven-shared/pull/6
> Maven Core resolves dependencies from reactor to build the graph (using
> http://maven.apache.org/ref/current/maven-core/xref/org/apache/maven/ReactorReader.html):
> this is sufficient when the graph is calculated after each reactor project
> has been compiled.
> But in case of Lifecycle participant (ie before any build action has taken
> place) or if we don't want to compile, this isn't sufficient
> Adding a method with extra parameters for such a limit-situation permits to
> hack for unresolved dependencies and replace them with projects collected
> from reactor
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
