Nexus hosted on repository.jboss.org has been upgraded from version 1.7.1 to 126.96.36.199. This upgrade brings numerous bug fixes and improvements to the web interface including an improved search. For a more details about the changes, see the jira release notes for Nexus 1.8.0 and Nexus 1.9.0.
As part of this upgrade we will also be regenerating all of the repository indexes. This process may take a few days to a week to complete for all of the repos, so please be patient if the search or other index related features are not fully functional at first.
Relevant to JBoss.org users, the Nexus archetype plugin is now a standard part of Nexus which should resolve some issues we've been facing with the generation of archetypes.xml.
This version of Nexus also comes with an improved UI for viewing audit information. You can now browse to an artifact in a repository in the Nexus UI, and select the "Artifact Information" tab. This will display the user who uploaded the artifact and the time which it was uploaded.
The older artifacts (migrated from the old repo) will not have the correct user and date information. The audit info for these artifacts is still availalbe via the audit.json files. We will be working in the coming weeks to migrate this information into the standard Nexus format.
We ran into an issue today where someone uploaded a bad version of a POM to the JBoss "thirdparty-uploads" repository. This was taking priority over the correct POM in central, and causing build issues. So here are some quick rules about how to correctly deploy to the JBoss Nexus repository.
Deploying a JBoss Project Release
If you are a developer of a JBoss project and you are uploading a project release you should upload to the staging URL
Deploy the artifact(s) the same way JBoss releases are deployed. Nexus will automatically stage these artifacts to go to the "thirdparty-releases" repository based on the Maven groupId.
Uploading a Thirdparty Binary Artifact
If you want to make a thirdparty released jar available in the JBoss repository, you should first check if the jar is already available in a thirdparty Maven repo. If yes, then you can request that a new proxy repository be added to repository.jboss.org using the JBBUILD jira project. The proxy repository can then be used via one of the main JBoss repo URLs.