[
https://issues.apache.org/jira/browse/MNG-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16983941#comment-16983941
]
Karl Heinz Marbaise commented on MNG-6763:
------------------------------------------
The updatePolicy is only for SNAPSHOT dependencies (or more accurate for
snapshot repositories) but not for releases. This can be circumvented by using
`mvn -U ..` on command line to force an update check on a repository if there
are newer SNAPSHOT versions available. Furthermore releases which already have
been downloaded will not checked on the repository manager again (based on the
updatePolicy which is usually set to {{never}} for releases).
Furthermore should your repository manager configured to pull the missing
dependencies from central repository...but this depends on the corporate
policy...
> Restrict repositories to specific groupIds
> ------------------------------------------
>
> Key: MNG-6763
> URL: https://issues.apache.org/jira/browse/MNG-6763
> Project: Maven
> Issue Type: New Feature
> Reporter: dennis lucero
> Priority: Major
>
> It should be possible to restrict the repositories specified in settings.xml
> to specific groupIds. Looking at
> [https://maven.apache.org/ref/3.6.2/maven-settings/settings.html#class_repository],
> it seems this is currently not the case.
> Background: We use Nexus to host our own artifacts. The settings.xml contains
> our Nexus repository with <updatePolicy>always</updatePolicy> because
> sometimes a project is built while a dependency is not yet in our Nexus repo
> – without updatePolicy, it would take 24 hours or manual deletion of metadata
> to make Maven re-check for the missing dependency.
> Additionally, we use versions-maven-plugin:2.7:display-dependency-updates in
> our build process.
> This results in lots of queries (more than 300 in a simple Dropwizard
> project) to our repo which will never succeed. If we could specify that our
> repo only supplies groupIds beginning with org.example, Maven could skip
> update checks for groupIds starting with com.fasterxml.jackson and so on,
> speeding up the build process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
