Closed rhoegg closed 10 months ago
Although the default deploy plugin seems to make the wrong filename for the signature file, I was able to upload the correct filename using the gpg plugin directly:
mvn gpg:sign-and-deploy-file -Dfile=dataweave-pq-0.1.0-dw-library.jar -DrepositoryId=ossrh -Durl=https://oss.sonatype.org/service/local/staging/deploy/maven2/ -DgroupId=software.hoegg -DartifactId=dataweave-pq -Dversion=0.1.0 -Dclassifier=dw-library -Dpackaging=jar -Dkeyring=0xF5C47901 -DpassphraseServerId=0xF5C47901 -Dgpg.executable="./gpghack.sh" -DpomFile=../pom.xml
I will see if I can complete the release this way and close the issue if so
This approach worked. We are available in maven central, and I added a badge to the README!
I've begun working on this but I am blocked by a strange behavior of the maven plugins for dataweave library, gpg, and install where the .asc file in the target folder gets a different filename when it is processed by install or deploy plugins. I initially reported the issue to sonatype, but then realized it is probably a problem with the dataweave library maven plugin.