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

POMs left in a modified state after failed release

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • m2release-plugin
    • None
    • Platform: HP, OS: Linux

      If the release plugin has run but the release failed, it leaves your POMs
      modified with the new version numbers. If your SCM uses update this will mean
      that subsequent builds (or releases) will see the modified version numbers.

      Apart from logging in and manually doing "svn revert", or just removing the
      workspace entirely, there is no easy way for a user to fix this after a failed
      release.

      Possibly this problem is related to the enhancement 3925.

            teilo James Nord
            ben_kelley ben_kelley
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: