Maven
  1. Maven
  2. MNG-1694

Build execution order control in fine grained projects.

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Incomplete
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Reactor and workspace
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      Currently in multi module projects you can only work in 2 modes.
      1) Build everything
      2) Build a single module, IF you have built and installed all its dependency modules

      I would like to be able to work the following way:
      1) Build everything
      2) Build an individual module, will build all the modules prior to it in the reactor list.
      3) Build a module module and all modules after it in the reactor list, will build missing prior modules.

      Use Case
      1) perform checkout and build
      2) module fails
      3) keep fixing module and running just its unit tests
      3) once all its unit tests pass build it and all modules after it in the reactor list. I don't need to build ones prior as they are unnaffected by the changes.

      In large mutli module projects this will save a LOT of time especially when you are gearing up for deployment and want to check that everything works - currently this is time consuming and repetitive, with much of the repetition uneeded.

        Issue Links

          Activity

          Hide
          Mark Proctor added a comment -

          To take real advantage of this we need project scoped repos.

          Show
          Mark Proctor added a comment - To take real advantage of this we need project scoped repos.
          Hide
          Brett Porter added a comment -

          I think what you really want here is

          • build this project and its dependencies inside this workspace
          • continue from last failed build

          Both reasonable ideas, but I also worry about introducing this kind of multi-mode operation too much. I would prefer to work on the ability to make some builds simply skip by as the files are unchanged. This makes the behaviour the same always and protects the user from their own error in not knowing what is updated.

          Show
          Brett Porter added a comment - I think what you really want here is build this project and its dependencies inside this workspace continue from last failed build Both reasonable ideas, but I also worry about introducing this kind of multi-mode operation too much. I would prefer to work on the ability to make some builds simply skip by as the files are unchanged. This makes the behaviour the same always and protects the user from their own error in not knowing what is updated.
          Hide
          Mark Proctor added a comment -

          skipping is fine by me, as long as its fast. Thats what I did for M1, I implemented my own build goal that iterates the reactor and calls jar:jar if a jar doesn't exist.

          Show
          Mark Proctor added a comment - skipping is fine by me, as long as its fast. Thats what I did for M1, I implemented my own build goal that iterates the reactor and calls jar:jar if a jar doesn't exist.
          Hide
          brianfox brianfox added a comment -

          This seems to be related to this proposal: http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode

          Show
          brianfox brianfox added a comment - This seems to be related to this proposal: http://docs.codehaus.org/display/MAVEN/Make+Like+Reactor+Mode
          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
          Hide
          Jason van Zyl added a comment -

          Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

          Show
          Jason van Zyl added a comment - Please refer to https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014 if you're wondering why this issue was closed out.

            People

            • Assignee:
              Unassigned
              Reporter:
              Mark Proctor
            • Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: