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
Problem: when releasing a version, packages are signed with GPG keys, but these packages do not exist yet. That causes that uploaded jar files are not uploaded with their asc files and Sonatype repo refuses to close the repository.
Version 2.0.0 was released without javadoc and sources - it is not a problem, because in this case the files are not useful for developers, but it would be more correct to have also these files in Maven Central.
The text was updated successfully, but these errors were encountered:
It was finally caused by duplicit javadoc and sources declarations which changed/deleted already signed files.
dmatej
changed the title
Move generation of javadoc and resources sooner in lifecycle
Sonatype repository checks fail to test gpg signs of javadoc and sources packages
Jan 31, 2018
Problem: when releasing a version, packages are signed with GPG keys, but these packages do not exist yet. That causes that uploaded jar files are not uploaded with their asc files and Sonatype repo refuses to close the repository.
Version 2.0.0 was released without javadoc and sources - it is not a problem, because in this case the files are not useful for developers, but it would be more correct to have also these files in Maven Central.
The text was updated successfully, but these errors were encountered: