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

0.10.0 eagerly tries to resolve image artifact on :tasks #235

Open
gavvvr opened this issue Sep 10, 2024 · 0 comments
Open

0.10.0 eagerly tries to resolve image artifact on :tasks #235

gavvvr opened this issue Sep 10, 2024 · 0 comments

Comments

@gavvvr
Copy link

gavvvr commented Sep 10, 2024

Hello. I've tried to migrate from 0.9.1 to 0.10.0 and faced the following issue: the new version unnecessarily tries to resolve reference image artifact too early. Consider the following minimalistic build.gradle.kts configuration:

plugins {
    id("java")
    id("maven-publish")
    id("build.buf") version "0.9.1"
}

buf {
    previousVersion = "0.0.1-SNAPSHOT"
    imageArtifact {
        groupId = "com.example"
        artifactId = "some-app"
        version = "0.0.1-SNAPSHOT"
    }
}

If you switch from 0.9.1 to 0.10.0 and try ./gradlew :tasks, Gradle will fail with the following error:

❯ ./gradlew :tasks

> Task :tasks FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':tasks'.
> Could not create task ':bufBreaking'.
   > Could not resolve all files for configuration ':bufBreaking'.
      > Cannot resolve external dependency com.example:some-app:0.0.1-SNAPSHOT because no repositories are defined.
        Required by:
            project :

I guess there is no need to resolve dependencies for bufBreaking, if you just want to get a list of tasks, but 0.10.0 has started doing that.

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

No branches or pull requests

1 participant