Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6074

Maven should produce an error if no model version has been set in a POM file used to build an effective model.

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

Details

    • Improvement
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • None
    • 3.5.0
    • None
    • None

    Description

      Maven currently only validates the model version to equal 4.0.0 when set. The XML element is optional. Starting with Maven 3.4.0 a warning message should be printed whenever no model version has been set so that it becomes possible to use that version to decide about Maven behaviour. For example: In Maven 3.5 we could add support for a new model version 4.1.0 which may be used to decide about how Maven 3.5 should behave. Behaviour for model version 4.0.0 will be the same as in Maven 3.4. Behaviour for model version 4.1.0 could be different. For this the model version needs to be set.

      Attachments

        Issue Links

        Activity

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

          People

            khmarbaise Karl Heinz Marbaise
            schulte77 Christian Schulte
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment