Skip to content

Lazily evaluate file paths for debug and instrumentation APKs #139

Open

Description

@julioz

debugApk and instrumentationApk are using the Gradle Property API, but still being evaluated in the configuration phase, preventing non-string references with the plugin configuration, for example:

fladle {
  debugApk = project.provider { findArtifactPath(some, parameters, here) }
}

Is this supposed to be fixed with #92 or is it a separate issue in the current plugin version?

Activity

  1. runningcode commented on Jan 22, 2021

    @runningcode
    Owner

    Related issue: calling isPresent eagerly evaluates properties: gradle/gradle#13932

    This feature may help alleviate this in the future: gradle/gradle#13401

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions