Agreed.
FYI, my resistence to declaring the sonatype repo in the top-level POM is twofold:
1) It will slow down the build, since *every* missing dependency will cause the sonatype repo
to be checked before Maven Central.
2) Given evidence that resolution from the sonatype repo *sometimes* works as it's currently
setup (i.e., declared only in the lucene test-framework POM), I am quite skeptical that adding
it to the top-level POM will help at all.
Steve
-----Original Message-----
From: dawid.weiss@gmail.com [mailto:dawid.weiss@gmail.com] On Behalf Of Dawid Weiss
Sent: Friday, September 07, 2012 8:25 AM
To: dev@lucene.apache.org
Subject: Re: SonaType repo in Maven POMs
> See my last post - sonatype repo is being used from lucene test-framework using the current
configuration.
I really don't know how maven artefact resolution order works but I
know Uwe and Robert had problems yesterday. But so did sonatype's repo
because there was a lot of HTTP 500 when trying to fetch updated
JARs...
Let's do this: next time I update, I'll let you know and you can experiment :)
Dawid
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
|