You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy (injected-nexus-deploy) on project pass-core-main:
Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.13:deploy failed: A message body reader for Java class
com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and Java type class
com.sonatype.nexus.staging.api.dto.StagingProfileRepositoryDTO, and MIME media type text/html was not found -> [Help 1]
This happens after
[INFO] [INFO] * Closing staging repository with ID "orgeclipsepass-1046".
[INFO]
[INFO] Waiting for operation to complete...
[INFO] ..................
[INFO]
[INFO] [INFO] Remote staged 1 repositories, finished with success.
[INFO] [INFO] Remote staging repositories are being released...
[INFO]
[INFO] Waiting for operation to complete...
Also note that despite the above failure, in every case the deployment to maven central has succeeded.
I spent a bunch of time digging into the source code. The maven plugin uses the Nexus 2 branch of https://github.com/sonatype/nexus-public. The REST API is based on Jersey. I wanted to see if the interactions could be made more reliable, but the interactions are buried in various abstractions. There are some timeouts that could be increased. See https://help.sonatype.com/repomanager2/staging-releases/configuring-your-project-for-deployment.
We should try setting stagingProgressTimeoutMinutes to something like 10 minutes, the default is 5.
One way to make things better is having the release process be able to be easily restarted.
Error in logs releasing pass-core:
This happens after
Also note that despite the above failure, in every case the deployment to maven central has succeeded.
These issues seem to be the same:
The text was updated successfully, but these errors were encountered: