Skip navigation
2010
Paul Gier

Nexus 1.7.1 Upgrade

Posted by Paul Gier Jul 22, 2010

We have completed the upgrade of our Nexus instance (https://repository.jboss.org/nexus/).  The upgrade went smoothly, however this upgrade requires a full rebuild of the Nexus index files.  The index generation seems to be resource intensive and is causing our Nexus instance to respond slowly to new requests.  This should be resolved sometime today when the index generation is complete.

 

There are some notable improvements in the new version.

  • The search interface is improved and you should no longer see messages like "too many results".
  • The staging repositories all all grouped together now, so you can just click on the "Staging Repositories" link to find your repo during a release.
  • Better handling of remote proxy repository failures.

 

Today we will be updating the wiki documentation which describes Nexus usage to relect changes in the new version.

If you've used repository groups in Nexus, you may have run into the issue where you see an artifact in a repository group and wonder "where did this artifact come from?"  In other words you would like to know which real (hosted) repository is actually storing the artifact.  Nexus allows you to see this and other debugging information with a spcial query at the end of the URL.  Just append "?describe" to the end of the URL of the file you are looking at.  For example, if you are looking at the jboss parent pom in the public repository group, and you want to see where it came from, the URL looks like this

 

https://repository.jboss.org/nexus/content/groups/public/org/jboss/jboss-parent/5/jboss-parent-5.pom?describe

 

The output is not well formatted, so it's a bit hard to read.  But if you look carefully you can find a field called "originatingRepositoryId" and this points to the "releases" repository.