Thanks for the reply Brian, this is much relief.
However in your initial response your wording clearly indicated the new policy
already being enforced, up to:
"[...] your artifacts will end up blocked."
A little less restrictive description could have prevented this
misunderstanding...
I think
>> Interesting. That's news to me... You have a pointer to more information?
>
As it turns out, almost all references to external repositories in
poms are junk or turn out to be junk after a bit of time. See here for
some examples:
http://www.sonatype.com/people/2010/03/why-external-repos-are-bein
On 03/23/2010 01:01 AM, Kevan Miller wrote:
On Mar 20, 2010, at 4:45 PM, Brian Fox wrote:
At the Central repository we are restricting the inclusion of external
repositories because this generally creates a mess. This is being
enforced on new artifacts coming in so I would recommend you do not
On Mar 20, 2010, at 4:45 PM, Brian Fox wrote:
> At the Central repository we are restricting the inclusion of external
> repositories because this generally creates a mess. This is being
> enforced on new artifacts coming in so I would recommend you do not
> add them or your artifacts themselves
We are having the same problem in Clerezza, one of the dependencies that
isn't in the central repo is sesame 2 [1]. I think we have the following
options:
- not include the sesame backend in the default distribution (users who need
it would have to compile it their selves of download it from elsew
At the Central repository we are restricting the inclusion of external
repositories because this generally creates a mess. This is being
enforced on new artifacts coming in so I would recommend you do not
add them or your artifacts themselves will end up blocked. A better
choice is to encourage the
I don't know of any apache policy regarding external repositories but i
usual don't recommend placing repositories into the POM at all.
Best practice is to use a repository manager and add the repositories there.
So, i am not sure how Apache Hudson is configured currently, but i would
suggest conne
Hi;
Is there any rule/policy for using third-party maven repositories in our
project poms? Recently, we have required to list some repositories in
settings.xml (for example: jboss) to our codebase built correctly. But when
Apache-Hudson runs to built daily, it throws errors because of not finding
