This is something that we dealt with specifically with a client with
Nexus. The Atlassian repositories were a complete mess (james tells me
this has been corrected), doing similar things with artifacts in
central and mixing snapshots and releases together. Nexus can actually
block requests for artifacts from a particular repository. So, in your
case you could block every request for an apache artifact from the
jboss repositories. With the routing in Nexus you can incrementally
block all the garbage that finds its way into public repositories.
Nexus first priority was to prevent crippling your internal
environment and protecting you from the outside world.
We plan to allow the general submission of these routing tables back
to our copy of Nexus running on our mirror of central so that open
source projects and people providing public repositories can clean up
their shit which adversely affects all Maven users.
I think all the metadata can be cleaned up inside 12 months, but until
then you have to protect your internal organization. With Nexus you
can group, route, and transform around problems. You group to order
and aggregate repositories behind one end point, you can route around
bad artifacts and crap repositories, and we dynamically rewrite
metadata on the fly to separate snapshot and release metadata so you
don't get hosed.
On 12-Apr-08, at 11:45 AM, Tom Huybrechts wrote:
Be careful with the jboss repository. It contains artifacts that have
the same groupId, artifactId and version as artifacts in central, but
with different content. Mixing both is asking for trouble...
Tom
On Fri, Apr 11, 2008 at 3:58 PM, Glynbach
<[EMAIL PROTECTED]> wrote:
Hi
I added the jboss repository to my POM to add a jta dependecy. But
running
mvn test gives an error retrieving the jta jar. The error shows
maven is
trying to get the jar from the maven repository (which exists but
has no jar
in it) rather than the jboss repository. Can I stipulate which
repository
should be used in the dependency?
pom entries are :
<project>
<repositories>
<repository>
<id>jboss</id>
<url>repository.jboss.com/maven2</url>
</repository>
</repositories>
..
<dependency>
<groupId>javax.transaction</groupId>
<artifactId>jta</artifactId>
<version>1.0.1B</version>
</dependency>
..
In the console I can see the following output:
----------
1 required artifact is missing.
for artifact:
com.fdar.apress.s2:app:war:1.0-SNAPSHOT
from the specified remote repositories:
jboss (repository.jboss.com/maven2),
central (http://repo1.maven.org/maven2)
and also:
url = http://repo1.maven.org/maven2
Downloading:
http://repo1.maven.org/maven2/javax/transaction/jta/1.0.1B/jta-1.0.1B.jar
[ERROR]
Thanks for any help
--
View this message in context:
http://www.nabble.com/Repository-search-order-tp16627819s177p16627819.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...
-- Thoreau
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
