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

Reject release of project containing undefined plugin versions

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • prepare, prepare-with-pom
    • None

    Description

      As discussed in slack, the m-release-p should reject releases where at least one plugin version was not set.

      The warning didn't cut it and can be removed once this is done, because it does not really matter for local builds – unless a dev uses an old maven version which leads to a bug, but then there is Maven Wrapper to rule that out.

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            bmarwell Benjamin Marwell

            Dates

              Created:
              Updated:

              Slack

                Issue deployment