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

Prevent sigstore-java from using "project" version when applied self #702

Open
loosebazooka opened this issue May 14, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working

Comments

@loosebazooka
Copy link
Member

When we apply sigstore-gradle-sign-plugin in build logic the sigstoreClientClasspath always wants to use the project dependency instead of the expected sigstore-java dependency of the plugin.

$ ./gradlew sigstore-java:dependencies --configuration sigstoreClientClasspath

> Task :sigstore-java:dependencies

------------------------------------------------------------
Project ':sigstore-java' - A Java client for signing and verifying using Sigstore
------------------------------------------------------------

sigstoreClientClasspath - Resolves Sigstore dependencies
+--- dev.sigstore:sigstore-java:0.7.0 -> project :sigstore-java (*)

see +--- dev.sigstore:sigstore-java:0.7.0 -> project :sigstore-java (*)

This can cause incompatibilities. Especially since the sigstore-gradle-sign-plugin version is 0.7.0.

This wouldn't be an issue once we're 1.0 and api stable. But it is a bit strange.

@loosebazooka loosebazooka added the bug Something isn't working label May 14, 2024
@loosebazooka
Copy link
Member Author

@vlsi not sure if you're aware of any workarounds, haven't been able to get any dependencyResolution to work here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants