Help

For those who were maybe not aware...

As of April 19, 2010, JBoss will be switching over its Maven repo infrastructure to utilize a repository manager (Nexus). Details of the change can be found here. Additionally there is a wiki page describing the new set up from the perspectives of both users and developers.

What does this mean for Hibernate user and developers specifically?

For user, not much really. You can continue to use the same release repository URL (http://repository.jboss.com/maven2) as we have been told it will remain active indefinitely. For the snapshot repository the story is a little bit different as the current snapshot repository URL (http://snapshots.jboss.org/maven2) will remain valid only for a few weeks. However, one gotcha you should be aware of is that the older release repository URL will still contain the (sometimes bad) copies of stuff from central. Using the newer URLs alleviates that.

For developers, well it means you have a few options:

  • You could use the JBoss repository as a proxy for many other repositories. Usually though this means adding a mirrorOf entry in your settings.xml which in turn means that the JBoss repo (with all its defined proxies) will be used for all of your builds. http://community.jboss.org/wiki/MavenRepositoryNexusConfiguration lists all the repositories currently proxied.
  • You could also just use the user snapshot repository URL and explicitly list any other repositories you want to use.
  • Yet another option that is just as valid for users is to set up a repository manager of your own locally and use it to proxy all the repositories you use. I have used this approach myself and it works out pretty well; I used Artifactory instead of Nexus however so I cannot speak to Nexus' capabilities or usage. If you are interested in this approach, the take a look at the following guides: Artifactory Guide, Nexus Guide
5 comments:
 
17. Apr 2010, 02:02 CET | Link
Sanne

very nice, this means we finally will be able to use proper indexes and search for updated jboss.org artifacts

ReplyQuote
 
17. Apr 2010, 16:38 CET | Link

Very Good news for me.

 
16. Jun 2010, 23:08 CET | Link
Arbi Sookazian

I just tried some searches here: https://repository.jboss.org/nexus/ and they all returned no results. Must we login to use this? If yes, what are the credentials?

 
17. Jun 2010, 04:26 CET | Link

Wow, you can actually get the http://repository.jboss.org/nexus page to load? You are ahead of me in the game ;)

As I mentioned in the article I am not a Nexus user, so to be honest I am not sure of the capabilities of this Nexus search. My attempts generally all resulted in a Too many results, please refine the search condition. message. A very pointed search for org.hibernate.FetchMode as a classname returned 420 matches, because of all the repos proxied not to mention the hosted repositories.

Try reading the Nexus docs, or asking on the #jbossas freenode channel or the #nexus codehaus channel.

 
17. Jun 2010, 07:06 CET | Link
Arbi Sookazian

Thx to some kind help from JP in #seam-dev channel, I figured it out. The following link works:

https://repository.jboss.org/nexus/index.html#nexus-search;gav~~aop~1.5.6.GA~~

If you search for keyword jboss-aop-jdk50-client in the artifact search, you'll get results in the search tab. Previously I was searching on foo.jar and that results in no hits. Seems to work pretty well now. I can view all the repos and everything. Nice!

Post Comment