Skip navigation
2011

As part of the upcoming process to start automatically syncing Maven artifacts between repository.jboss.org and Maven central (repo1.maven.org) we will be enforcing several artifact validation rules.  In the past we have had problems with some of the Nexus validation rules, but these issues should now be resolved.  The validation rules currently in effect are the following:

 

Artifact Uniqueness Validation - Each staged artifact in a release must be unique to prevent uploading duplicate files.

Checksum Validation - The uploaded checksum of each file is checked against the file.

POM Validation - Several fields of the POMs are validated.

Sources Validation - There must be a -sources.jar file for each uploaded binary jar.

 

More information about the staging rules are available in the Nexus Book.  Before staging any release, please check that your project configuration matches the JBoss.org Maven Project Configuration Requirements.

 

In addition, it will eventually be required that all artifacts uploaded to repository.jboss.org include a valid PGP signature.  I'll be adding information about how to do this to the wiki, and probably write a separate blog post.  For information about how to generate a PGP signature for your project files, see the Maven GPG plugin.

The repository.jboss.org Nexus repository indexes and the search features of the repository now seem to be working correctly.  We've had multiple problems in the past correctly generating repository indexes, but after upgrading to Nexus 1.9.0.2 and migrating away from our old audit plugin (now replaced by the standard Nexus upload tracking), the index generation works correctly.  The repository search also has an improved UI and seems significantly faster than our old Nexus configuration.

 

NexusSearchScreenshot.png