[MNG-6112] Align artifacts and plugins policies using the default value

[jira-importer]

Christian Schulte opened MNG-6112 and commented

---

Affects: 3.5.0-beta-1

Issue Links:

• MNG-4645 Move Central repo definition out of Maven's jars so it can be more easily changed
  ("Is contained by")
• MNG-8019 Streamline update policy of pluginRepository/repository of Maven Central in Super POM

Remote Links:

• Page
  
• GitHub Pull Request #145
  
• GitHub Pull Request #1142
  
• GitHub Pull Request #145
  

Backported to: 4.0.0-alpha-7

1 votes, 9 watchers

[jira-importer]

Stephen Connolly commented

Maven 3.4.0 has been dropped. See this thread for more details.

This issue will need to be re-scheduled for a Maven release in the (hopefully near) future.

[jira-importer]

Christian Schulte commented

Issue is fixed in the master branch of my private maven repository on github. When interested, you can cherry pick the commit to your own repository and create a pull request for the apache master branch with just this commit yourself from there.

[jira-importer]

Pascal Schumacher commented

It would be very nice if this was released in 3.5.1.

[jira-importer]

Robert Scholte commented

I'm missing the reason why this has to be changed. I should dive into this issue, but some old blog matches the way I think the never-policy should work. I don't think that's what we want.

[jira-importer]

Stephen Connolly commented

I too fail to see why this is desirable at all. Can you please provide a justification as to why we would want the metadata from central to never be updated by default?

I am inclined to resolve this as WONTFIX

[jira-importer]

Manfred Moser commented

I agree that this seems like a bad idea. If anything I would go with always .. provided its performance overhead is not too bad. I would leave as is for now though.

[jira-importer]

Robert Scholte commented

Closed as Won't Fix based on comments

[jira-importer]

Michael Osipov commented

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.