Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
3.1.1
-
None
-
None
Description
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.