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.

Sign up for GitHub

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

Jump to bottom

Lazily evaluate file paths for debug and instrumentation APKs #139

Open

julioz opened this issue Jun 15, 2020 · 1 comment

Contributor

julioz commented Jun 15, 2020 •

edited

Loading

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?

The text was updated successfully, but these errors were encountered:

pawelpasterz mentioned this issue

[FLADLE] Lazily evaluate file paths for debug and instrumentation APKs Flank/flank#1486

Closed

Owner

runningcode commented Jan 22, 2021

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