Skip to content

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

@gavvvr

Description

@gavvvr

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions