[jira] [Comment Edited] (MNG-6667) Hint at Maven upgrade requirement when trying to build a pom.xml with a newer modelVersion

["Hervé Boutemy (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16853679#comment-16853679 ] 

Hervé Boutemy edited comment on MNG-6667 at 6/26/19 8:04 PM:
-------------------------------------------------------------

https://gitbox.apache.org/repos/asf?p=maven.git;a=commit;h=01405a2d60ec44f9c11843a8f904822a9ed280fc


was (Author: stephenc):
https://gitbox.apache.org/repos/asf?p=maven.git;a=shortlog;h=refs/heads/mng-6667

> Hint at Maven upgrade requirement when trying to build a pom.xml with a newer modelVersion
> ------------------------------------------------------------------------------------------
>
>                 Key: MNG-6667
>                 URL: https://issues.apache.org/jira/browse/MNG-6667
>             Project: Maven
>          Issue Type: Improvement
>          Components: core
>            Reporter: Stephen Connolly
>            Assignee: Stephen Connolly
>            Priority: Major
>              Labels: maven-5.x-preparation
>             Fix For: 3.6.2
>
>
> In order to allow us to bump the modelVersion *for building* we need Maven to alert users about the updated building requirements.
> NOTE: We will always need to *deploy* a modelVersion 4.0.0 pom.xml so that consumers can consume dependencies, but we can *build* with a newer model version and produce the corresponding modelVersion 4.0.0 pom.xml for deployment (this would be flattened so that it has no parent). The build pom only needs to be deployed if it is being used as a parent, in which case:
> * The pom using it as a parent will have to have a newer or same modelVersion as its parent
> On that basis we can either 
> * Deploy the newer modelVersion parent pom with a classifier and its 4.0.0 (best-effort) equivalent without a classifier, then when building the child, we look for the parent with classifier and only if missing do we fall back to look for a modelVersion 4.0.0 parent.
> * Deploy the newer modelVersion parent pom as normal, since you need to have a newer modelVersion to be a child and we only deploy flattened 4.0.0 compatibility poms for the children, no legacy consumer will ever have to parse the parent
> Determination of which of these two approaches to use is out of scope for this issue.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)