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

Refresh verification-metadata.xml file to fix dokka failures #1145

Closed
wants to merge 1 commit into from
Closed

Refresh verification-metadata.xml file to fix dokka failures #1145

wants to merge 1 commit into from

Conversation

rciovati
Copy link
Contributor

Description

This PR should address the build failures in #1144:

Dependency verification is an incubating feature.
> Task :buildSrc:generateExternalPluginSpecBuilders FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':buildSrc:generateExternalPluginSpecBuilders'.
> Dependency verification failed for configuration ':buildSrc:compileClasspath'
  2 artifacts failed verification:
    - dokka-gradle-plugin-0.10.1.jar (org.jetbrains.dokka:dokka-gradle-plugin:0.10.1) from repository MavenRepo
    - dokka-gradle-plugin-0.10.1.pom (org.jetbrains.dokka:dokka-gradle-plugin:0.10.1) from repository MavenRepo
  This can indicate that a dependency has been compromised. Please carefully verify the checksums.

  Open this report for more details: file:///Users/riccardociovati/ghq/github.com/pinterest/ktlint/build/reports/dependency-verification/at-1620742605343/dependency-verification-report.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 621ms

To refresh the metadata file, I've just deleted the old one and created a new one with the command suggested in the report:

./gradlew --write-verification-metadata pgp,sha256 help --refresh-dependencies

Checklist

  • tests are added
  • CHANGELOG.md is updated

@chao2zhang
Copy link
Contributor

In my opinion, a better approach is to upgrade dokka version

@rciovati
Copy link
Contributor Author

@chao2zhang I don't disagree on that. However, it looks like that upgrading Dokka requires more work than just bumping the library version so I guess that needs a separate investigation. With this PR I just want to make the build green again.

@shashachu
Copy link
Contributor

@rciovati I'll take a look at the dokka update this week.

@shashachu
Copy link
Contributor

Closing in favor of #1148

@shashachu shashachu closed this May 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants