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

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

This can be implemented with MNG-6763.

> Ability to set repository of dependency
> ---------------------------------------
>
>                 Key: MNG-6612
>                 URL: https://issues.apache.org/jira/browse/MNG-6612
>             Project: Maven
>          Issue Type: New Feature
>          Components: Dependencies
>            Reporter: Max Lee
>            Priority: Minor
>              Labels: Repository, dependency
>
> In a setup where you specify multiple different repositories for your project 
> it would be a useful to be able to specify which repository contains which 
> dependency in the pom and not resolve such dependencies from the general 
> repositories but only the ones defined for the dependency.
> E.g. in cases where you don't want other dependencies to get resolve in 
> certain repositories because they contain broken versions or when you simply 
> want to stop the potential privacy/security issues that leaking dependencies 
> to another repository that doesn't even include the dependency could 
> introduce. (Theoretically an ignored/skip-repositories setting could also 
> solve this issue) Another application of this feature could be to define 
> different update or checksum check setting for different artifacts that would 
> use the same repository.
> This could theoretically be setup using the repository name:
>  
> {code:java}
> <dependency>
>     <groupId>id.group</groupId>
>     <artifactId>artifact-id</artifactId>
>     <version>version-string</version>
>     <repositories>
>         <repository>repository-id</repository>
>     </repositories>
> </dependency>
> {code}
> or by allowing to directly set the repository-settings in the dependency and 
> not on the outer scope (this would allow for a wider range of applications by 
> allowing different repository settings per artifact but require a larger 
> config for simply setting the repository of an artifact)
>  
> {code:java}
> <dependency>
>     <groupId>id.group</groupId>
>     <artifactId>artifact-id</artifactId>
>     <version>version-string</version>
>     <repositories>
>         <repository>
>             <id>repository-id</id>
>             <url>https://repo.example.com/</url>
>         </repository>
>     </repositories>
> </dependency>
> {code}
>  
>  
>  



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

Reply via email to