Re: Restrict a groupId to a specific reposirory

Fabrice, that is the recommended, in fact you can't mix hosted and proxy in Nexus. This is more about optimizing Nexus to know where (or where not) to look for artifacts. For example, if Maven makes a request for a company snapshot that doesn't exist yet, even if you have the repos ordered in your group correctly, Nexus will fall down the list looking for it, including looking in any public snapshot repos. This is also true when proxying metadata since Nexus will look in all repos and then merge the results. Using the routing rules, lets you tell Nexus that com.yourcompany.* can only ever be located in your internal hosted repos. This is a performance enhancement, as well as it doesn't leak any info about internal development outside your org.

On Mon, Jun 29, 2009 at 12:02 PM, Fabrice Mercier <fabrice.mercier.pro@gmail.com> wrote:

nice
But I read it is better to use a repo for private artifact (mycompany) separated from others (external proxiied). Scheduled task Tasks can be different etc...

2009/6/29 Damian Bradicich <dbradicich@...>

Craig, sure you can do that, checkout the book

 

http://www.sonatype.com/books/nexus-book/reference/config.html#config-sect-managing-routes

 

Damian

On Mon, Jun 29, 2009 at 11:45 AM, Craig Cook <craig.cook@...> wrote:

Hi. Does anyone know if there is a way to restrict requests for a specific groupId (com.mycompany) to a specific repository (mycompanyrepo)?
This way it won’t go hitting public repos looking for private company code (artifacts).

Cheers,

Craig Cook | Business Technology Consultant | BT Design:DSO | Tel: +44 (0)2078 095 948 | Ext: 6505948 | Mob: +44 (0)7918 880 501 | E-mail craig.cook@... | Web: craigcook.co.uk boycook.com

--
Cordialement / Best regards

Fabrice Mercier