Skip to content

ApolloTaskWithClasspath is not cacheable if different Gradle log level options are used #6398

Closed
@lwasyl

Description

@lwasyl

Version

4.0.0

Summary

I know 4.0.0 is not the most recent release, but I think the issue is still there.

Here, Apollo plugin will construct options with the first enabled Gradle logger level:

Eventually here, this log level is a task input:

I may be wrong but I don't think log level affects the task outputs, and as such shouldn't be an input to the task? The problem with current implementation is that ./gradlew <apolloGeneratingTask> and ./gradlew <apolloGeneratingTask> --quiet will not reuse the cache because task inputs have changed.

Steps to reproduce the behavior

No response

Logs

(Your logs here)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions