maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Olaf Otto (Jira)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6763) Restrict repositories to specific groupIds
Date Tue, 02 Jun 2020 09:29:00 GMT

    [ https://issues.apache.org/jira/browse/MNG-6763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17123562#comment-17123562
] 

Olaf Otto commented on MNG-6763:
--------------------------------

I'd like to add my five cents to this feature request. I think it would be extremely valuable
to have such restrictions in place. We, for instance, are in a situation where we have projects
with artifacts provided by and shared with multiple different stakeholders featuring their
own nexus repositories for their internal artifacts. Permission to the respective nexus repos
is granted on a per-user basis. There is no sensible way to centralize this via a mirror.

Resulting, we have dozens of queries per artifact going out to each of these repos, which
*considerably* slows down artifact resolution.

To me, it is clear that specific repositories are not meant to serve any, but only specific
artifacts, a restriction of a repo to specific groupIds in a settings.xml seems like an obvious
solution - in fact I came here to file the very same request. I'd also offer to help with
it's implementation.

> 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)

Mime
View raw message