Hi Vincent, I believe I identified the problem. One needs to use -Papache-release instead of -Prelease. This generates the signatures, adds the javadoc jars etc. The new staging repo is here:
https://repository.apache.org/content/repositories/shindig-staging-016/ There are issues with GPG signing: [INFO] gpg: WARNING: "--no-use-agent" is an obsolete option - it has no effect I activated gpg-agent to sign the artifacts Also, I saw some of this: [INFO] 2248K uploaded (shindig-1.1-BETA2-incubating-20090805.182435-1-source.tar.bz2) [INFO] [INFO] Retrieving previous build number from apache.snapshots.https [INFO] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '1b057e58e68f7c078a43613ad7707bc55ded538c'; remote = 'd23c06917f48efc3c8c5d2ade24681dd2def1da7' - RETRYING [INFO] [WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '1b057e58e68f7c078a43613ad7707bc55ded538c'; remote = 'd23c06917f48efc3c8c5d2ade24681dd2def1da7' - IGNORING [INFO] Uploading: https://repository.apache.org/content/repositories/snapshots/org/apache/shindig/shindig/1.1-BETA2-incubating-SNAPSHOT/shindig-1.1-BETA2-incubating-20090805.182435-1.pom.asc Any clues? On Tue, Aug 4, 2009 at 5:59 PM, Vincent Siveton <[email protected]> wrote: > 2009/8/4 Paul Lindner <[email protected]>: > > Okay, I'll see if I can get these issues ironed out. I followed the > > instructions in the releasing shindig page to the letter... > > Hehe! maybe I missed something :) > > > BETA1 was withdrawn, but rather than mangle JIRA I kept it as a > 'withdrawn' > > release. > > Good point for jira, but since we have no beta-1 I guess it avoids... > Anyone? > > > Not sure where the .asc files are, I assume those are generated by the > gpg > > signing process? > > I think so too > > > Is it possible that some of the artifacts are being pulled from my local > > maven repo? My first dry-run failed, however I did a regular mvn install > > in-between. > > Did you call Maven with -DdryRun? > > Cheers, > > Vincent >
