Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sonatype repository checks fail to test gpg signs of javadoc and sources packages #2

Closed
dmatej opened this issue Jan 6, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@dmatej
Copy link
Member

dmatej commented Jan 6, 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.

@dmatej dmatej added the bug label Jan 6, 2018
@dmatej dmatej added this to the v2.0.1 milestone Jan 6, 2018
@dmatej dmatej self-assigned this Jan 6, 2018
dmatej added a commit that referenced this issue Jan 31, 2018
@dmatej dmatej closed this as completed Jan 31, 2018
@dmatej
Copy link
Member Author

dmatej commented Jan 31, 2018

It was finally caused by duplicit javadoc and sources declarations which changed/deleted already signed files.

@dmatej 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant