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

Guillaume Nodet commented on MNG-8190:
--------------------------------------

That would be nice, but I'm not sure it's feasible.

The first problem is that the resolver is used before building the main model 
when downloading Maven extensions.

The second problem is that we could have mixed modelVersions and I don't think 
we can change during the resolution (afaik).  We could assume a fixed value and 
look at the root project's modelVersion I suppose.

Also this would work only when building projects.  When consuming, the intent 
of the developer would not be followed, as this would mean each dependency 
should be resolved differently.

So I'm not saying we can't, but I'm not really sure that it will actually 
lessen the disruption.

This is slightly related to the discussion we had with [~cstamas] about how to 
enable new cool features from the resolver by default (split repositories, 
etc...), though the problem with repositories is the interaction between Maven 
3 and Maven 4.

> Restrict build pom feature to 4.1.0 model version
> -------------------------------------------------
>
>                 Key: MNG-8190
>                 URL: https://issues.apache.org/jira/browse/MNG-8190
>             Project: Maven
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 4.0.0-beta-3
>            Reporter: Karl Heinz Marbaise
>            Assignee: Guillaume Nodet
>            Priority: Major
>             Fix For: 4.0.0-beta-5
>
>
> Currently I can omit the version tag in a parent definition (or dependency) 
> in a module with ModelVersion:4.0.0 which is not correct.
> This should fail with an appropriate failure message even in Maven 4.0.0+ 
> We should allow omitting the version tag (parent) in a module only for Maven 
> 4+ with the ModelVersion 4.1.0 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to