[
https://issues.apache.org/jira/browse/MNG-4173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426703#comment-17426703
]
Alan Czajkowski edited comment on MNG-4173 at 10/9/21, 9:22 PM:
----------------------------------------------------------------
[~bironran2] you're asking for the build to have inconsitency (developer build
_must_ be different from CI build) ... this is terrible in practice, you end up
with situations where the developer says "I don't know why it's broken in CI,
works on my machine", you should strive to make your builds as consistent as
possible across all use-cases, I know many people in the industry are doing
short-cuts (NPM is notorious for this, and they're paying the price), but in
the end all of these short-cuts lead to pain
was (Author: alan-czajkowski):
[~bironran2] you're asking for the build to have inconsitency (developer build
_must_ be different from CI build) ... this is terrible in practice, you end up
with situations where the developer says "I don't know why it's broken in CI,
works on my machine", you should strive to make your builds as consistent as
possible across all use-cases, I know many people in the industry are doing
short-cuts (NPM is notorious for this, and they're paying the price), but in
the ned all of these short-cuts lead to pain
> 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)
