[
https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17427294#comment-17427294
]
Ran Biron commented on MNG-4173:
--------------------------------
[~alan-czajkowski] I think that's a very "ivory tower" approach. You're right
that it _might_ cause issues and that _maybe_ there will be an eventuality
where a developer will complain. However, the use case I provided is real and
exists right now. The effects of not "taking the shortcut" are significant and
will require workarounds in source control management and release process to
maintain developer productivity.
> 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)
