Maven Release Plugin
  1. Maven Release Plugin
  2. MRELEASE-150

Can't add prefix to tags without affecting version

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.0-beta-4
    • Fix Version/s: None
    • Component/s: perform
    • Labels:
      None

      Description

      I added the following to my POM

      <plugin>
      <artifactId>maven-release-plugin</artifactId>
      <configuration>
      <tag>XXX-$

      {artifactId}-${version}</tag>
      </configuration>
      </plugin>

      However the tag comes out incorrectly.

      [INFO] Full run would be tagging C:\PerforceViews\... with label: 'XXX-myproject-0.5.4-SNAPSHOT

      What is the default? <tag>${artifactId}

      -$

      {version}

      </tag>
      Note: this seems to be missing from the plugin documentation, it only mentions releaseLabel, which defaults to tag.

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Closed Closed
          1774d 19h 52m 1 stephenconnolly 24/Jun/11 08:18
          Mark Thomas made changes -
          Workflow jira [ 12961758 ] Default workflow, editable Closed status [ 12998538 ]
          Mark Thomas made changes -
          Project Import Mon Apr 06 00:52:26 UTC 2015 [ 1428281546237 ]
          Mark Thomas made changes -
          Workflow jira [ 12723975 ] Default workflow, editable Closed status [ 12763160 ]
          Mark Thomas made changes -
          Project Import Sun Apr 05 12:15:05 UTC 2015 [ 1428236105845 ]
          stephenconnolly made changes -
          Resolution Duplicate [ 3 ]
          Status Open [ 1 ] Closed [ 6 ]
          Hide
          Stephen Connolly added a comment -

          Closing as duplicate of MRELEASE-159

          Show
          Stephen Connolly added a comment - Closing as duplicate of MRELEASE-159
          Hide
          hanasaki jiji added a comment -

          Could this be made more generic allowing for SVN and GIT versions as well?
          ex: blahblah-v1.2.0-r756.jar

          Show
          hanasaki jiji added a comment - Could this be made more generic allowing for SVN and GIT versions as well? ex: blahblah-v1.2.0-r756.jar
          Jeff Skjonsby made changes -
          Attachment release-manager-patch.patch [ 50167 ]
          Hide
          Jeff Skjonsby added a comment -

          Here's a patch with unit tests that adds simple substitution for [groupId], [artifactId], and [version] in the release label.

          Show
          Jeff Skjonsby added a comment - Here's a patch with unit tests that adds simple substitution for [groupId] , [artifactId] , and [version] in the release label.
          Maria Catherine Tan made changes -
          Link This issue is related to CONTINUUM-2266 [ CONTINUUM-2266 ]
          Arnaud HERITIER made changes -
          Component/s perform [ 13616 ]
          Hide
          Sergio Fernandes added a comment -

          I have the same problem: I need to add a suffix to make the release tag match our naming pattern.

          Adding these variables seems to be very easy and valuable.

          Show
          Sergio Fernandes added a comment - I have the same problem: I need to add a suffix to make the release tag match our naming pattern. Adding these variables seems to be very easy and valuable.
          Joerg Schaible made changes -
          Field Original Value New Value
          Link This issue relates to MRELEASE-159 [ MRELEASE-159 ]
          Hide
          Roberto Lo Giacco added a comment -

          It would be very nice to allow for something like

          <tag>XXXXX-$

          {project.relase.version}

          </tag>

          Any hint how it can be performed?

          Show
          Roberto Lo Giacco added a comment - It would be very nice to allow for something like <tag>XXXXX-$ {project.relase.version} </tag> Any hint how it can be performed?
          Hide
          Yuri Schimke added a comment -

          Just realised, the default is obviously null, so that it prompts you to enter the label.

          So its actually set at a point that understands the various versions. Can this be addressed by adding extra variables that can be referenced i.e.

          • version.previous
          • version.release
          • version.next
          Show
          Yuri Schimke added a comment - Just realised, the default is obviously null, so that it prompts you to enter the label. So its actually set at a point that understands the various versions. Can this be addressed by adding extra variables that can be referenced i.e. version.previous version.release version.next
          Hide
          Mike Perham added a comment -

          I suspect the variables are getting resolved during the POM snapshot -> release transform so that the <tag> value is then hardcoded to that value, no longer using variables.

          Show
          Mike Perham added a comment - I suspect the variables are getting resolved during the POM snapshot -> release transform so that the <tag> value is then hardcoded to that value, no longer using variables.
          Yuri Schimke created issue -

            People

            • Assignee:
              Unassigned
              Reporter:
              Yuri Schimke
            • Votes:
              18 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development