[
https://jira.codehaus.org/browse/MNG-5582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=340972#comment-340972
]
Jason van Zyl commented on MNG-5582:
------------------------------------
Implemented in 8d489a2deb33cb7a6dcd87277c5d4476d458deaf
> Continue to track all the projects in the reactor even if the set is
> constrained by --projects
> ----------------------------------------------------------------------------------------------
>
> Key: MNG-5582
> URL: https://jira.codehaus.org/browse/MNG-5582
> Project: Maven 2 & 3
> Issue Type: Improvement
> Affects Versions: 3.1.1
> Reporter: Jason van Zyl
> Fix For: 3.2
>
>
> 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
(v6.1.6#6162)
