You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Schulte (JIRA)" <ji...@apache.org> on 2016/07/31 16:46:20 UTC

[jira] [Updated] (MNG-6074) Maven should produce an error if no model version has been set in a POM file used to build an effective model.

     [ https://issues.apache.org/jira/browse/MNG-6074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schulte updated MNG-6074:
-----------------------------------
    Summary: Maven should produce an error if no model version has been set in a POM file used to build an effective model.  (was: Maven should print a warning if no model version has been set in a POM file.)

> Maven should produce an error if no model version has been set in a POM file used to build an effective model.
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-6074
>                 URL: https://issues.apache.org/jira/browse/MNG-6074
>             Project: Maven
>          Issue Type: Improvement
>            Reporter: Christian Schulte
>            Assignee: Christian Schulte
>            Priority: Critical
>             Fix For: 3.4.0
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)