You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2021/06/28 06:29:00 UTC

[jira] [Closed] (MNG-7178) Why can't Maven set content like Gradle to handle multiple repositories

     [ https://issues.apache.org/jira/browse/MNG-7178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Osipov closed MNG-7178.
-------------------------------
    Resolution: Duplicate

> Why can't Maven set content like Gradle to handle multiple repositories
> -----------------------------------------------------------------------
>
>                 Key: MNG-7178
>                 URL: https://issues.apache.org/jira/browse/MNG-7178
>             Project: Maven
>          Issue Type: Improvement
>          Components: Dependencies
>    Affects Versions: 3.8.1
>            Reporter: zxiaozhou
>            Priority: Major
>         Attachments: image-2021-06-28-13-41-30-778.png
>
>
> Maven requires multiple repositories to be configured, partly depending on the location of the repository. Why can't Maven set some groupids like Gradle to go to a specific dependency repository.
> For example, the Gradle configuration:
> !image-2021-06-28-13-41-30-778.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)