[
https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17433057#comment-17433057
]
Ran Biron commented on MNG-4173:
--------------------------------
[~alan-czajkowski]Â I'll capitulate to "broken". But the way it is right now
(broken or as designed) works well for our flow. All I'm requesting is for a
way to preserve this, even using a special flag
"–iReallyGiveUpOnReproduciableBuildsLetMeUseReleaseVersionForDependencies".
Making the change as you've described might have a technical benefit, but in
our project that won't translate to any other kind of benefit and splitting the
modules will cause us extra headache with multi-project release management
"just" because the build process for one part is more demanding (in resources,
licenses, etc) than another part.
> 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)
