[
https://issues.apache.org/jira/browse/MNG-6112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231619#comment-17231619
]
Michael Osipov edited comment on MNG-6112 at 11/13/20, 4:44 PM:
----------------------------------------------------------------
I am reopening this because our approach is inconsistent:
https://github.com/apache/maven/blob/master/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml#L38-L51
Why is the policy for plugins set to never, but for regular artifacts. What
makes a plugin JAR different from a dependency JAR? I'd expect full consistency
here.
was (Author: michael-o):
I am reopening this because our approach is inconsistent:
https://github.com/apache/maven/blob/master/maven-model-builder/src/main/resources/org/apache/maven/model/pom-4.0.0.xml#L38-L51
Why is the policy for plugins set to never, but for regular artifacts. What
makes a plugin JAR different from a dependency JAR?
> Central repository in the 4.0.0 super POM should declare update policy
> 'never'.
> -------------------------------------------------------------------------------
>
> Key: MNG-6112
> URL: https://issues.apache.org/jira/browse/MNG-6112
> Project: Maven
> Issue Type: Bug
> Affects Versions: 3.5.0-beta-1
> Reporter: Christian Schulte
> Assignee: Robert Scholte
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
