[
https://issues.apache.org/jira/browse/MNG-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888105#comment-17888105
]
Didier Loiseau commented on MNG-8190:
-------------------------------------
Following [~khmarbaise]’s argument, I think the same should apply to the
dependency management logic implemented in MNG-7982, i.e. the default value of
{{maven.resolver.dependencyManagerTransitivity}} should be {{true}} only for
4.1.0+.
Otherwise a pom built with Maven 3 could potentially get different dependencies
when built with Maven 4. Keeping the Maven 3 behavior for Model Version 4.0.0
would probably help smoothing the transition.
What do you think [~gnodet]?
> 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)