[ https://issues.apache.org/jira/browse/MNG-6082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15746401#comment-15746401 ]
Mark Struberg commented on MNG-6082: ------------------------------------ Well, I didn't want to offend anyone. It seems that a lot of work have been put into it. But nonetheless I was not able to find any answer to what this ticket is about without looking at all the linked tickets. I think it's good to have as a summary ticket, but it should at least have a description. I've looked through the list of tickets and I could not find a ticket which requires us to bump the pom model version. There are quite a few underspecified areas (optional in dependencyManagement, etc) where I agree that it should get nailed better. But still nothing which requires a version bump imo. Can you point me to any new pom tag or attribute (and the corresponding ticket)? If there is none, then there is also no need to bump the version. Re the dependencyManagement clarifications: we might need at least a compatibility flag in the maven CLI to allow older projects to still build with their 'broken' poms. Just an idea... > Introduction of model version 4.1.0 > ----------------------------------- > > Key: MNG-6082 > URL: https://issues.apache.org/jira/browse/MNG-6082 > Project: Maven > Issue Type: New Feature > Reporter: Christian Schulte > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
