You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Tamas Cservenak (Jira)" <ji...@apache.org> on 2022/10/25 20:12:00 UTC
[jira] [Closed] (MRESOLVER-167) Support forcing specific repositories for artifacts
[ https://issues.apache.org/jira/browse/MRESOLVER-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tamas Cservenak closed MRESOLVER-167.
-------------------------------------
Resolution: Fixed
> Support forcing specific repositories for artifacts
> ---------------------------------------------------
>
> Key: MRESOLVER-167
> URL: https://issues.apache.org/jira/browse/MRESOLVER-167
> Project: Maven Resolver
> Issue Type: New Feature
> Components: Resolver
> Reporter: Vasiliy Kudriavtsev
> Assignee: Tamas Cservenak
> Priority: Major
> Fix For: 1.9.0
>
>
> We need the ability to enforce searching for specfic artifacts (for example, artifacts with a certian group id or a group id matching a wildcard) from specific repositories
> Use case:
> # We use both public and local repositories. For security reasons I want maven never to search public repositories for our internal artifacts as I do not want to reveal there names
> # Performance. If I have to use several repositories and I know in advance where certain artifacts can be found, I would like to use this knowedge not to search in vain.
> #
> If maven maintainers are ok with the idea, I can go ahead and write a design document
--
This message was sent by Atlassian Jira
(v8.20.10#820010)