Continuum
  1. Continuum
  2. CONTINUUM-1504

when autoVersionSubmodules=true is defined in the pom for the release plugin, the release prepare screen should not show or allow changing of child project versions

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.1-beta-3
    • Fix Version/s: 1.3.2 (Beta)
    • Component/s: Release
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      90% of the time the defaults for the versions are correct, however when I need to use a different value i have to make the change in too many places on the screen. when using the release plugin, it only asks me for the parent versions and propgates them down automatically. i would assume the release prepare screen would do the same and not have inputs available to put in child pom versions.

        Issue Links

          Activity

          Hide
          Emmanuel Venisse added a comment -

          Done in r.741440

          Show
          Emmanuel Venisse added a comment - Done in r.741440
          Hide
          Wendy Smoak added a comment -

          What is the expected behavior after this change?

          I tried it at r741440 with examples/mm-example in the sandbox, which has 'autoVersionSubmodules' set to true, and I still see it prompting for a version for both mm-parent and the mm-core submodule.

          Here's the project:
          http://svn.apache.org/repos/asf/continuum/sandbox/examples/mm-example/

          This Selenium test shows the steps I used:
          http://svn.apache.org/repos/asf/continuum/trunk/continuum-webapp-test/src/test/selenium-ide/test_release_plugin_configuration.html

          (It's possible that Continuum isn't reading correctly from the pom – I don't see the comment prefix show up on the release prepare page either. See CONTINUUM-2028 and CONTINUUM-2054)

          Show
          Wendy Smoak added a comment - What is the expected behavior after this change? I tried it at r741440 with examples/mm-example in the sandbox, which has 'autoVersionSubmodules' set to true, and I still see it prompting for a version for both mm-parent and the mm-core submodule. Here's the project: http://svn.apache.org/repos/asf/continuum/sandbox/examples/mm-example/ This Selenium test shows the steps I used: http://svn.apache.org/repos/asf/continuum/trunk/continuum-webapp-test/src/test/selenium-ide/test_release_plugin_configuration.html (It's possible that Continuum isn't reading correctly from the pom – I don't see the comment prefix show up on the release prepare page either. See CONTINUUM-2028 and CONTINUUM-2054 )
          Hide
          Emmanuel Venisse added a comment -

          It works fine for me on my sample multi-module project. I'll try with your sample.

          The expected behaviour is to print the value of the 'autoVersionSubmodules' if it is set in the POM and to prompt only for the parent POM version if is is set.

          Show
          Emmanuel Venisse added a comment - It works fine for me on my sample multi-module project. I'll try with your sample. The expected behaviour is to print the value of the 'autoVersionSubmodules' if it is set in the POM and to prompt only for the parent POM version if is is set.

            People

            • Assignee:
              Emmanuel Venisse
              Reporter:
              Tomislav Stojcevich
            • Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: