Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.0
-
Fix Version/s: 1.1
-
Labels:None
-
Number of attachments :
Description
Currently, the dependencies file only contains the dependencies in the current project. However, in cases where we're releasing a multi-module project all at one go, it would be nice to support collecting all dependencies from sub-modules, winnowing out the inter-module dependencies, and using that collection for generating the dependencies file instead of only those dependencies of the current project.
It also may make more sense in these cases to mimic the assembly plugin's runOnlyAtExecutionRoot flag, and only process the remote resources once for a project tree.
Issue Links
- depends upon
-
MSHARED-126
Create shared api to resolve project dependencies
-
Needs an integration test. Apparently it's not running ONLY at execution root...instead, it aggregates at the execution root when runOnlyAtExecutionRoot is set, and runs normally for other projects in the build...this is obviously wrong.