This message was deleted.
# wiremock-java
s
This message was deleted.
👍 1
o
@Tom You still need to copy over the bits to
build.gradle
, like extracting GPG and Nexus creds. I hope to finish the convention plugin next week, and then it should becime much easier\
t
Still can’t believe how hard this is in 2023
o
It is much easier with Maven
But oh yes, we will get it better
t
First time anyone’s ever said that 😂
😃 1
o
https://github.com/wiremock/wiremock-state-extension/blob/develop/build.gradle for the example. You will need to add env var resolution to GPG and Nexus publishi
First time anyone’s ever said that
I am the guy who likes checked exceptions. Wjhat would you expect from me 😛
t
I suspect there’s a strong correlation between liking checked exceptions and liking Maven 🙂
😛 1
o
@Tom "Received status code 409 from server: Conflict" means you need to burn and increment the version
t
I’m close I think. Just needed to delete the half completed build from my last attempt.
o
I normally just change the version, because GitHub has some eventual consistency when deleting packages
🤮 1
This is why I tripled the number of releases in the Extension State Plugin, especially when I hit the Gradle 8 bug. Sorry @Dirk Bolte 🙂
t
This should be possible in a one-liner in this day and age. I’m speechless that it’s taken me nearly a day to get this working.
Any idea why this might have happened?
Where does Sonatype go to find valid signer keys?
I’ve got that in the build, but that’s not what I mean - where does Nexus find what it considers a valid key?
Did we hand that over via Jira when setting up the release bot account with Sonatype?
o
Yes, the key is registered with Nexus for the release bot
It is on one of the open source keyrings and verified
t
I wonder if the issue is that I’ve previously released this with my own key
Where can I grab a copy of the key? Would like to try validating locally.