A brand new error appeared on a build configuration that has been working and stayed unchanged for months, and I'm trying to trace the source of evil. My theory is that it may be a new requirement on Sonatype/Maven Central that javadoc jars need .asc signature, and the publishSigned task hasn't changed to accommodate that.
Failed to close the repository
[error] Activity close started:2018-06-22T15:49:27.111Z, stopped:
[error] Failed: signature-staging, failureMessage:Missing Signature: '/com/outworkers/phantom-connectors_2.12/2.24.7/phantom-connectors_2.12-2.24.7-javadoc.jar.asc' does not exist for 'phantom-connectors_2.12-2.24.7-javadoc.jar'.
java.lang.Exception: Failed to close the repository
While the error is self explanatory, the cause is less so.
- Is the
publishSigned task supposed to automatically sign all artifacts, including javadoc jars?
- If not, how can I force it or require the plugin to do the doc jar signing by default? I haven't been able to find specifics in the doc, apologies in advance if this will turn out to be a case of rtfm.
Regards,
Flv.
A brand new error appeared on a build configuration that has been working and stayed unchanged for months, and I'm trying to trace the source of evil. My theory is that it may be a new requirement on Sonatype/Maven Central that javadoc jars need
.ascsignature, and thepublishSignedtask hasn't changed to accommodate that.While the error is self explanatory, the cause is less so.
publishSignedtask supposed to automatically sign all artifacts, includingjavadocjars?Regards,
Flv.