[
https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17215099#comment-17215099
]
Alan Czajkowski commented on MNG-4173:
--------------------------------------
[~bironran] based on what you've said here and in StackOverflow, your "problem"
is begging for the "solution" to be: pull out the "annoying" module into its
own repo/build/project, independent of the main multi-module project
> 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: Issues to be reviewed for 4.x
>
>
> 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)
