Thank you!

[stephanpelikan]

I just wanted to say thank you 👍 for sharing your findings:

https://github.com/otto-de/jlineup#publishing-to-sonatypes-central-publisher-portal-was-challenging

It saved me a lot of time during publishing 🚒 since the error is totally misleading. I have reported the error to Central Portal support ⛑. I hope they will update their documentation.

Cheers,
Stephan

[MediaMarco]

Thank you for saying thank you and for the report to Sonatype. :)

Best,
Marco

[MediaMarco]

@stephanpelikan btw, did the support answer and are they planning to fix this issue?

[stephanpelikan]

This is my support request:

Hello,

We have migrated from OSSRH to Central Portal. When publishing I got this error:

Failed to process deployment: Error on building manifests: No Archiver found for the stream signature Details: No Archiver found for the stream signature

Thanks to this guy Marco who shared his findings about the error and how to solve it, I could also solve it by removing all executable JARs:

https://github.com/otto-de/jlineup#publishing-to-sonatypes-central-publisher-portal-was-challenging

I don’t know how he figured out, but based on the information given (the error and component-files section is empty, see screenshot attached) it is nearly impossible to find the error’s cause. Please update the documentation (e.g. https://central.sonatype.org/publish/requirements/) to reflect this change.

Thanks,
Stephan Pelikan from VanillaBP

This is the response:

Hello vanillabp,

Thanks for the feedback i escalated this to the team and there is an active discussion on trying to figure out how to proceed with this case and similar cases. We are glad to hear you were able to find a workaround in the meantime though

Regards,
The Central Team

Unfortunately, no planning information. I moved our executable JARs into the projects Github-release pages for download and updated our documentation. This is not ideal but OK to me.