[ https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17422421#comment-17422421 ]
Ran Biron commented on MNG-4173: -------------------------------- [~alan-czajkowski] that's a non solution. are you seriously telling me to change the entire project structure because maven can't look an artifact tagged release? besides, I'd still have to change tagging every time I release that other project instead of relying on snapshots. > Remove automatic version resolution for POM plugins > --------------------------------------------------- > > Key: MNG-4173 > URL: https://issues.apache.org/jira/browse/MNG-4173 > Project: Maven > Issue Type: Task > Components: Plugins and Lifecycle > Affects Versions: 3.0-alpha-3 > Reporter: Benjamin Bentmann > Priority: Major > Fix For: 4.0.x-candidate > > > Maven 3.x will no longer try to automatically find the version for plugins > specified in the POM, i.e. the effective POM must declare a version for each > plugin used for the sake of reproducible builds. Omitting the plugin version > will raise in error. -- This message was sent by Atlassian Jira (v8.3.4#803005)