Uploaded image for project: 'Continuum'
  1. Continuum
  2. CONTINUUM-1312

Build trigger issue in multimodule project

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Duplicate
    • 1.1-alpha-2
    • None
    • Core system
    • None

    Description

      If you have a multimodule project with the parent pom at the top level directory, e.g.:

      + pom.xml
      +- module1
      +- pom.xml
      +- module2
      +- pom.xml
      Etc

      Then, a modification to any module will trigger the build of ALL modules.
      This is obviously because a change in a module will be detected at the top level, and that if the top level is modified, all its subprojects are rebuilt.

      A solution may be to put the parent POM at the same level as the others, but this triggers other problems...
      It would be nice to a solution at the continuum level.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. CONTINUUM-1606 All modules are always rebuilt when using M2 with a hierarchical structure

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. CONTINUUM-1400 in a multi-module build, Continuum should tell SCM to exclude submodules to reduce the amount of unnecessary updates

          • Major - Major loss of function.
          • Closed

          Activity

            People

              brett Brett Porter
              julien Julien Le Dem
              Votes:
              8 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: