If gpg:sign-and-deploy-file doesn't work for some reason, it's tempting to try manual upload of artifacts instead. passing these properties ( -D): url, repositoryId, file, pomFile, classifier.
use a generic pom ( -f) (configure maven-gpg-plugin and nexus-staging-maven-plugin ( is the latter needed here?)).pass settings configured for GPG signing and OSSRH account ( -s).for each *.pom, *.jar, *-sources.jar and *-javadoc.jar.copy relevant section of prepared repo into current hudson workspace.manually jar it up and put it into the location expected by maven.Workaround for sources artifacts missing for 8 artifacts ( bug 510976). copy the jar to the locations so that it will be picked up by maven.create a README.txt referring to the doc bundle.Use a heuristic mapping from bundle name to name of the doc bundle holding corresponding javadoc, one of: