gradle-release icon indicating copy to clipboard operation
gradle-release copied to clipboard

After migrating to a new Mac, release task no longer signs artifacts

Open sbabcoc opened this issue 5 years ago • 0 comments

I have a mature project from with I've published many releases: https://github.com/Nordstrom/Selenium-Foundation

Prior to the current revisions I'm trying to publish, I released my builds from a Windows machine. For the release I need to publish now, I'm attempting to publish the build from a new Mac machine. Nothing has changed about the gradle.build file itself. The only difference is the migration from my previous machine to my new machine. I think I reproduced my old setup on the new machine, but there's clearly something that's not configured correctly.

The generated POM file gets signed as expected, but none of the other artifacts (JAR, JavaDoc, and source) are getting signed. Running the build task with debug output, I see messages about the signing tasks for these artifacts being "realized", but not ASC files are produced or published. I can run the signing tasks manually, and the ASC files are generated as expected, but these are not published with the rest of the artifacts even if they are available.

What can I do to diagnose this problem and fix it?

sbabcoc avatar Mar 04 '20 20:03 sbabcoc