On 17/03/2008, at 9:44 AM, Jason van Zyl wrote:
On 16-Mar-08, at 3:28 PM, Brett Porter wrote:
On 17/03/2008, at 6:03 AM, Jason van Zyl wrote:
All control must reside in the repository manager or it's a
configuration nightmare.
Sorry, but I have to disagree. A repository manager is an
optimisation (and best practice) in using Maven, but not a pre-
requisite. Let's not forget the people that just want to build some
OSS project that depends on other repositories.
There are people I know like Bruce Snyder and Brian who use
Proximity for their own person local repository. Even for open
source you're soon going to start seeing them using repository
managers as the primary means of sharing their wares.
I'm not saying it's not a good idea. It's in my best practices slides,
along with the single URL mirrorOf and using the enforcer (which I'd
like to start using for weeding out repos you don't want as well).
I do exactly the same as Bruce and Brian, running Archiva on my
machine 24x7. It picks up all the crappy Maven ITs that depend on
repository definitions that Brian is fixing, and nuisance builds that
crawl out all over the place, and gives me a super-easy way to test
staged releases with the addition of a flag to the build.
I currently funnel everything in to a single repository for
convenience and use white/blacklists, but I think with Nicolas' change
in place I would move to 1-for-1 and that would make sure I knew if a
build wouldn't work outside of a repository managed environment while
still optimising what I have.
I think this thread was about Nicolas' change specifically, so I'll
start a new one to discuss what I think we need to do in Maven itself.
- Brett
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
