Uploaded image for project: 'Maven Release Plugin'
  1. Maven Release Plugin
  2. MRELEASE-723

DCVS tagging commands should store the tag-name (or hash) in the the //project/scm/tag element.

    XMLWordPrintableJSON

Details

    • New Feature
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.3
    • Git, Mercurial, Subversion
    • None
    • Patch

    Description

      With SVN the developerConnection and connection are
      updated to the "real" release URL, that is when I invoke release:prepare with
      a URL like:
      https://SVNSERVER/svn/REPO/myproject/branches/release it will be
      replaced by https://SVNSERVER/svn/REPO/myproject/tags/myproject-1.0
      which is fine because now you know which revision to checkout for
      building the release.

      With git there is no such possibility to realize this with rewriting
      the URL AFAIK. So I would have expected however, that maybe the //project/scm/tag
      element would be updated to reflect the fact, that the pom is the one
      of release, either to the "symbolic name" myproject-1.0 or to the hash
      of the tag.

      See http://markmail.org/thread/m77cvhqqq56krzzd as well.

      Attachments

        1. testprj-svn-repo.zip
          36 kB
          Mark Struberg
        2. testpr-git.zip
          39 kB
          Mark Struberg
        3. MRELEASE-723-idea.patch
          4 kB
          Mark Struberg
        4. add-tag-to-release-poms-1329108.patch
          24 kB
          Mirko Friedenhagen
        5. add-tag-to-release-poms.patch
          24 kB
          Mirko Friedenhagen

        Activity

          People

            struberg Mark Struberg
            mfriedenhagen Mirko Friedenhagen
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: