[
https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17432760#comment-17432760
]
Alan Czajkowski edited comment on MNG-4173 at 10/22/21, 1:43 AM:
-----------------------------------------------------------------
[~bironran2] this is not an "ivory tower" approach, judging by the depth of the
explanation you have provided here and elsewhere, it is clear that the
"development process" is broken for this project ... the tool (Maven) isn't the
problem here, it is the process and architecture of the project that is the
problem ... I have spent the better part of a decade re-building broken
projects like this across many industries and various-sized organizations
was (Author: alan-czajkowski):
[~bironran2] this is not an "ivory tower" approach, judging by the depth of the
explanation you have provided here and elsewhere, it is clear that the
"development process" is broken for this project ... the tool (Maven) isn't the
problem here, it is the process and architecture of the project that is the
problem
> 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)
