[
https://issues.apache.org/jira/browse/MNG-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17271268#comment-17271268
]
Michael Osipov commented on MNG-6763:
-------------------------------------
I have experienced this myself at work where I have setup a business unit
hosted repo with group id partitioning. I.e., you can acess only parts of it
and you know upfront that !com/company/ will not in this repo. I like to
explore possible solutions to this, but first I don't want to conflate with
availability of snapshots because this isn't really related to me here.
So, repositories in settings and POM and structurally identical (as [~jfallows]
has pointed out), I will treat them as such in this discussion. Could something
like {{maven-common-artifact-filters}} be utilized by Maven Core/Resolver like
many other plugins do? When resolver iterates oder the download requests I
would apply the filter to find out whether this repo is eligible for download.
WDYT?
What would be your ideas from a configuration point of view?
> 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
> Labels: intern
>
> 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)
