flow: Gradle task ":vaadinPrepareFrontend" does not cache results

Describe the bug

The “:vaadinPrepareFrontend” does not cache if the source and dependencies did not change, causing increasingly long compile times on incremental builds on another project.

This shows when running the build with the --info flag:

Task ':projectName:vaadinPrepareFrontend' is not up-to-date because:
  Task has not declared any outputs despite executing actions.

Expected-behavior

When running successive builds without changing a file, the output of “:vaadinPrepareFrontend” is identical, so there is no need to execute it twice.

Reproduction

  • Have two Vaadin applications in the same multimodule Gradle project
  • Execute two successive build commands on the project root (the default when using IntelliJ)
  • See that the “:vaadinPrepareFrontend” command is not “UP-TO-DATE” even if the files did not change

System Info

Windows 10, Java 17, Vaadin 23.2.0 Gradle:

  • Version: 7.4
  • Vaadin plugin version: 23.2.0
  • Build cache: Disabled
  • Config cache: Disabled
  • Parallel builds: Disabled

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 3
  • Comments: 15 (8 by maintainers)

Commits related to this issue

Most upvoted comments

This would be great to get done. It would be an improvement for sure, and with all the improvements done to caching in Gradle 8 which just released this makes sense.

Incremental builds for vaadinPrepareFrontend task is included into Flow 24.2.0.alpha4 pre-release and will be available in the next Vaadin platform pre-release. vaadinBuildFrontend doesn’t include this feature yet. We will see if this could be target 24.2 or postponed to a next minor 24.3.