Closed mikera closed 11 years ago
Hmmm just seen the note in the README. This answers my question - though I think the issue is still valid!
Indeed. Still working out the kinks with the release process. Will mark this issue as resolved once I'm able to make it available. Gpg's a confusing bugger.
On Friday, February 22, 2013, Mike Anderson wrote:
Hmmm just seen the note in the README. This answers my question - though I think the issue is still valid!
— Reply to this email directly or view it on GitHubhttps://github.com/bpsm/edn-java/issues/28#issuecomment-13922903.
I got maven-gpg-plugin working on a few of my projects.... let me know if you want some tips!
Here's a parent pom with maven-gpg-plugin set up properly that you may want to take a look at.
My troubles were not with configuring the plugin, but rather with the fact that sonatype couldn't verify the key I signed with. I published it to one of the servers mentioned in the error message and then things worked.
Specifically, this, which I'd done initially when I registered with sonatype was not enough:
$ gpg --keyserver hkp://pool.sks-keyservers.net --send-keys 7A81A310
gpg: sending key 7A81A310 to hkp server pool.sks-keyservers.net
But, this seemed to do the trick:
$ gpg --keyserver hkp://keyserver.ubuntu.com --send-keys 7A81A310
gpg: sending key 7A81A310 to hkp server keyserver.ubuntu.com
https://keyserver.ubuntu.com is one of the key servers that the sonatype release validation process actually uses to verify the key used to sign the artifacts.
I was then able to sign and deploy the artifacts by hand:
mvn -Pgpg gpg:sign-and-deploy-file \
-Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ \
-DrepositoryId=sonatype-nexus-staging \
-DpomFile=pom.xml \
-Dfile=target/edn-java-0.4.0.jar
mvn -Pgpg gpg:sign-and-deploy-file \
-Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ \
-DrepositoryId=sonatype-nexus-staging \
-DpomFile=pom.xml \
-Dfile=target/edn-java-0.4.0-sources.jar \
-Dclassifier=sources
mvn -Pgpg gpg:sign-and-deploy-file \
-Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ \
-DrepositoryId=sonatype-nexus-staging \
-DpomFile=pom.xml \
-Dfile=target/edn-java-0.4.0-javadoc.jar \
-Dclassifier=javadoc
and these were acceptable.
edn-java 0.4.0 is now available in the sonatype releases repository: https://oss.sonatype.org/content/repositories/releases/
Specifically, here: https://oss.sonatype.org/content/repositories/releases/us/bpsm/edn-java/0.4.0/
I've commented on OSSRH-4597 to activate central sync, so I assume it will show up in maven central in a few days provided the sonatype people find no issues.
Great stuff - just tried out 0.4.0 release and everything seems to be working well....
I wanted to try out the new 0.4.0 release, but wasn't able to find it on any of the usual public repos (Clojars, Maven Central). I could only find the snapshot versions.
Are the releases available anywhere that I should be aware of?
If not, I think they should be - it makes it much easier for people to pick up and run with the library