Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Auto Closed
    • Affects Version/s: 2.0-beta-9
    • Fix Version/s: None
    • Component/s: prepare
    • Labels:
      None
    • Environment:
      2.0

      Description

      I don't see any solution how to execute plugins before question like "What is the release version for" appears.

      Current "preparationGoals" are executed later.
      Also command line sequence like mvn plugin:task... release:prepare do not help.

      I suppose that many users would like to manage project.version before questions are displayed.

      In my example i tried to run buildnumber-maven-plugin or maven-scm-plugin to retrieve last $

      {buildNumber}

      or $

      {scm.revision} . This number I would like use in final release number. Plugins under release are not executed.

      BTW.
      release:prepare execute scm (svn) so it also could return revision status in standard variable named ${scm.revision}

        Activity

        Hide
        Krashan Brahmanjara added a comment -

        My feature request is - add parametr "initGoals" for tasks executed on start.

        For example :
        Instead command -
        mvn buildnumber:create release:prepare
        user should run only
        mvn release:prepare with parameter <initGoals>buildnumber:create</initGoals>

        Show
        Krashan Brahmanjara added a comment - My feature request is - add parametr "initGoals" for tasks executed on start. For example : Instead command - mvn buildnumber:create release:prepare user should run only mvn release:prepare with parameter <initGoals>buildnumber:create</initGoals>
        Hide
        Michael Osipov added a comment -

        This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

        Show
        Michael Osipov added a comment - This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

          People

          • Assignee:
            Unassigned
            Reporter:
            Krashan Brahmanjara
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development