Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17778

Allow to specify module versions when releasing multi module projects

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Duplicate
    • Icon: Major Major
    • m2release-plugin
    • None

      When releasing a multi-module project all child projects get assigned the version of the parent.

      It would be great if they took the version of their pom or if there was a way to specify the version.

      Is there another way of releasing multi-module projects in which the modules have different versions than the parent?

          [JENKINS-17778] Allow to specify module versions when releasing multi module projects

          Massimiliano Turri created issue -
          Massimiliano Turri made changes -
          Summary Original: Allow to specify module versions when deploying multi module projects New: Allow to specify module versions when releasing multi module projects

          Massimiliano Turri added a comment -

          After further investigation it seems that, at the maven execution level, the problem with multi-module projects is due to the provided properties: developmentVersion and releaseVersion. When these properties are provided the versions of the child modules are forced to be identical to the version of the parent project.

          The m2release plugin provides the configuration option "Default versioning mode". At the moment it seems that it does not allow users to change it from its default value of "None" which seems to correspond to allowing users to specify one single version for all modules.

          One simple solution might be to allow users to choose as default versioning something like "let maven pick" which would correspond to a maven execution command without the properties "developmentVersion" and "releaseVersion".

          In this instance the versions should be picked up from the pom files of each of the sub-modules.

          Thanks!

          Massimiliano Turri added a comment - After further investigation it seems that, at the maven execution level, the problem with multi-module projects is due to the provided properties: developmentVersion and releaseVersion. When these properties are provided the versions of the child modules are forced to be identical to the version of the parent project. The m2release plugin provides the configuration option "Default versioning mode". At the moment it seems that it does not allow users to change it from its default value of "None" which seems to correspond to allowing users to specify one single version for all modules. One simple solution might be to allow users to choose as default versioning something like "let maven pick" which would correspond to a maven execution command without the properties "developmentVersion" and "releaseVersion". In this instance the versions should be picked up from the pom files of each of the sub-modules. Thanks!

          James Nord added a comment - - edited

          JENKINS-11466

          James Nord added a comment - - edited JENKINS-11466
          James Nord made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          James Nord made changes -
          Link New: This issue duplicates JENKINS-11466 [ JENKINS-11466 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 148958 ] New: JNJira + In-Review [ 192960 ]
          James Nord made changes -
          Assignee Original: James Nord [ teilo ]

            Unassigned Unassigned
            turri Massimiliano Turri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: