Maven Remote Resources Plugin
  1. Maven Remote Resources Plugin
  2. MRRESOURCES-41

add support for multi-module dependencies listing and other top-of-tree calculations on sub-modules

    Details

    • Type: New Feature New Feature
    • Status: Closed
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: 1.0
    • Fix Version/s: 1.1
    • Labels:
      None

      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

          Activity

          John Casey created issue -
          John Casey made changes -
          Field Original Value New Value
          Fix Version/s 1.0.1 [ 15148 ]
          John Casey made changes -
          Fix Version/s 1.1 [ 14382 ]
          Fix Version/s 1.0.1 [ 15148 ]
          John Casey made changes -
          Priority Major [ 3 ] Blocker [ 1 ]
          John Casey made changes -
          Assignee John Casey [ jdcasey ]
          Resolution Fixed [ 1 ]
          Status Open [ 1 ] Closed [ 6 ]
          John Casey made changes -
          Link This issue depends upon MSHARED-126 [ MSHARED-126 ]
          Hide
          John Casey added a comment -

          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.

          Show
          John Casey added a comment - 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.
          John Casey made changes -
          Resolution Fixed [ 1 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          John Casey made changes -
          Status Reopened [ 4 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 12:17:56 UTC 2015 [ 1428236276684 ]
          Mark Thomas made changes -
          Link This issue depends upon MSHARED-126 [ MSHARED-126 ]
          Mark Thomas made changes -
          Workflow jira [ 12724749 ] Default workflow, editable Closed status [ 12763912 ]
          Mark Thomas made changes -
          Project Import Mon Apr 06 00:55:18 UTC 2015 [ 1428281718795 ]
          Mark Thomas made changes -
          Link This issue depends upon MSHARED-126 [ MSHARED-126 ]
          Mark Thomas made changes -
          Workflow jira [ 12962478 ] Default workflow, editable Closed status [ 12998509 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          8d 7h 19m 1 John Casey 27/Aug/09 19:09
          Closed Closed Reopened Reopened
          14d 16h 47m 1 John Casey 11/Sep/09 11:56
          Reopened Reopened Closed Closed
          6m 56s 1 John Casey 11/Sep/09 12:03

            People

            • Assignee:
              John Casey
              Reporter:
              John Casey
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development