On 08/09/2009, at 10:33 PM, EJ Ciramella wrote:
So that's kind of a pain, no? Having to list things that should be
coming from the codehaus repository in all the blacklists of every
other
repository?
Is this truly the only way to do this?
I see you're point and personally I'd rather all these rules were in a
central location.
The best approach to the current situation is to use whitelists on
every repository (in which case blacklists for those not in that list
are not necessary). Only on repositories such as central where you
generally want everything except corporate artifacts do I use a
blacklist typically.
- Brett
-----Original Message-----
From: Brett Porter [mailto:[email protected]] On Behalf Of Brett
Porter
Sent: Friday, September 04, 2009 10:17 AM
To: [email protected]
Subject: Re: making sure archiva goes exactly where you want it to
On 05/09/2009, at 12:10 AM, EJ Ciramella wrote:
Hello list,
I'm struggling with a problem where other repositories that we're
proxing for are scanned for our internal things we've installed into
our own repository.
Is there an easy way to say, "if you're looking for package
com.foo.bar, only ever go to <internal repository>"?
Not quite, but the reverse.
Add com/foo/bar/** to the blacklist for the repositories you don't
want
it to go to.
- Brett
