[ https://issues.apache.org/jira/browse/MNG-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17880029#comment-17880029 ]
Karl Heinz Marbaise commented on MNG-8190: ------------------------------------------ I would second the support for build/consumer based on Model Version 4.1.0+ which makes it from my point of view more clear that this is related to Maven 4.0.0+ otherwise you can create a pom file and accidently trying to build with Maven 3.X which will fail! That would make it easier to separate Maven 3 vs. Maven 4 from user perspective. > Omitting version tag in Parent/Dependency - ModelVersion 4.0.0 > -------------------------------------------------------------- > > Key: MNG-8190 > URL: https://issues.apache.org/jira/browse/MNG-8190 > Project: Maven > Issue Type: Bug > Components: Core > Affects Versions: 4.0.0-beta-3 > Reporter: Karl Heinz Marbaise > 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)