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

Some tasks do not support up-to-date checks #649

Open
lfielke opened this issue Nov 17, 2021 · 0 comments · May be fixed by #811
Open

Some tasks do not support up-to-date checks #649

lfielke opened this issue Nov 17, 2021 · 0 comments · May be fixed by #811

Comments

@lfielke
Copy link

lfielke commented Nov 17, 2021

A really nice feature of Gradle is incremental builds, where tasks don't need to be executed unless they would do something useful. The tasks InstallFeatureTask and DeployTask run even if nothing has changed in the project directory. They shouldn't need to run because installing the same thing twice should result in the same result.

The easiest way to demonstrate is to run libertyCreate or deploy twice in a row without changing any files.

For me, the InstallFeatureTask takes approx 1.3 seconds to execute, DeployTask 12 ms, the first is a significant proportion of the whole build time.

The Gradle documentation about up to date checks: https://docs.gradle.org/current/userguide/more_about_tasks.html#sec:up_to_date_checks

A Gradle build scan says about InstallFeatureTask:

The task was not up-to-date because it did not have any declared outputs.

DeployTask has the same message about no declared outputs.

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

Successfully merging a pull request may close this issue.

1 participant