[jira] [Commented] (MNG-5582) Continue to track all the projects in the reactor even if the set is constrained by --projects

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069508#comment-17069508 ] 

Hudson commented on MNG-5582:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> Continue to track all the projects in the reactor even if the set is constrained by --projects
> ----------------------------------------------------------------------------------------------
>
>                 Key: MNG-5582
>                 URL: https://issues.apache.org/jira/browse/MNG-5582
>             Project: Maven
>          Issue Type: Improvement
>    Affects Versions: 3.1.1
>            Reporter: Jason van Zyl
>            Priority: Major
>             Fix For: 3.2.1
>
>
> Currently we are throwing away the original set of projects when --projects is used to constrain the set of projects. They should be kept in the even they need to be used. One use case I have is reducing the number of projects being built, but still be able to access the contents of other projects in the reactor. In my case a type of workspace resolution from the command line where I build a set of projects but resolve resolve dependencies from the co-located projects instead of going to the local repository.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)