You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2007/03/28 16:58:35 UTC
[jira] Updated: (MNG-2608) configure a repository as the
'preferred' download location for certain artifactIds or groupIds
[ http://jira.codehaus.org/browse/MNG-2608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jason van Zyl updated MNG-2608:
-------------------------------
Fix Version/s: 2.1-alpha-1
This is in-line with some of the things discussed with Jason Dillon and the Geronimo builds. Specifically where we have rogue repositories for axis and tomcat which don't work and we need to provide some control to the user to avoid theses abuses which makes builds un-buildable. We have the extreme case where G 1.1.1 won't build because some stuff was removed from repositories they have to use.
> configure a repository as the 'preferred' download location for certain artifactIds or groupIds
> -----------------------------------------------------------------------------------------------
>
> Key: MNG-2608
> URL: http://jira.codehaus.org/browse/MNG-2608
> Project: Maven 2
> Issue Type: Improvement
> Reporter: Jorg Heymans
> Fix For: 2.1-alpha-1
>
>
> ivy has this feature where you can tell it where an artifact is located. During dependency resolution, this avoids a lot of unnecessary http lookups to the configured repositories while searching for the artifact because it will go straight to the correct one.
> in pom speak:
> <repository>
> <releases>
> <enabled/>
> <updatePolicy/>
> <checksumPolicy/>
> </releases>
> <snapshots>
> <enabled/>
> <updatePolicy/>
> <checksumPolicy/>
> </snapshots>
> <id/>
> <name/>
> <url/>
> <layout/>
> <preferredFor>
> <groupId>org.apache.cocoon</groupId>
> <artifactId>my.special.artifact</artifactId>
> </preferredFor>
> </repository>
> If the groupid or artifactid was not found on the 'preferred' server then you could still try and contact the other configured repositories ofcourse.
> As an example: output of artifact resolution in cocoon while looking for an updated snapshot
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from snapshots
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from reinhard-m2-snapshot-repository
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from central
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from apache.snapshot
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from apache-cvs
> [INFO] snapshot org.apache.cocoon:cocoon-deployer-plugin:1.0.0-M2-SNAPSHOT: checking for updates from apache.snapshots
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira