New Maven repositories

sanne.grinovero · **Posted:** Sun Jul 25, 2010 12:00 pm

The Maven repository for JBoss projects, which includes the Hibernate artifacts, was recently changed:

https://repository.jboss.org/nexus/content/groups/public/

Old artifacts are still to be found in the old repositories, but to get access to new releases use the new URL.

See the announcement on the Hibernate blog for more info and pointers to the recommended Maven configuration:
http://relation.to/Bloggers/JBossMavenRepositoryChanges

JVerstry · **Joined:** Wed Aug 04, 2010 3:10 pm **Posts:** 1

Sorry, my bad about Sonatype, but the -Final issue and the documentation issues remains. Together with empty/incomplete directories such as https://repository.jboss.org/nexus/cont ... 5.4-Final/ for example.

steve · **Posted:** Wed Aug 04, 2010 5:15 pm

Huh? JBoss runs its own Nexus repository, which is where we publish our artifacts. We have nothing to do with oss.sonatype.org

steve · **Posted:** Wed Aug 04, 2010 8:59 pm

There is no missing artifacts and/or empty/incomplete directories.

http://in.relation.to/Bloggers/Hibernate350FinalRelease#comment16528
http://in.relation.to/Bloggers/Hibernate350FinalRelease#comment16530
http://in.relation.to/Bloggers/Hibernate350FinalRelease#comment16532

edalquist · **Joined:** Thu Oct 06, 2005 7:34 pm **Posts:** 20

Reposting the content from viewtopic.php?f=1&t=1010979 here since this is about the new maven repo:

We are getting reports from all of our developers and our CI build server about regular "Connection refused" errors from https://repository.jboss.org This is becoming very problematic for our developers.

The errors that we are getting look like the following.

Code:

Could not transfer artifact org.hibernate:hibernate-entitymanager:jar:3.6.4.Final from/to jboss-public-repository-group (https://repository.jboss.org/nexus/cont ... /releases/): Error transferring file: Connection refused

It isn't just the entitymanager, it seems like the jboss repository just randomly fails when maven is trying to connect to it. If I wait and try again a half dozen times eventually maven can get all the hibernate artifacts from the Jboss repository but this problem makes our nightly build tool report failures quite often.

Is this a know issue with the jboss.org repository? Is there a better place I should to report this?

sanne.grinovero · **Posted:** Thu May 19, 2011 5:10 pm

I'm going to answer on the other post, so we can discuss in a proper thread.

Celestejonas · **Joined:** Wed Sep 21, 2011 9:34 am **Posts:** 6

You no longer need to worry about having the JBoss repo referenced because all JBoss
artifacts have been cleaned up and migrated to Maven Central.