feat: gather Flow and Hilla Gradle tasks under vaadin group #1996
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This gathers all available Gradle tasks from
Hilla and Flow plugins under one task group
"Vaadin". Also, this gets rid of all the
duplicate extension parameters from
EngineProjectExtension
.The
EngineProjectExtension
instance thatcurrently being exposed to users as
hilla
can remain the same to show which
parameters are related to which set of tasks,
for example, if the users wants to set the
exposedPackagesToParser
, that shouldbe set via
hilla
extension:vs. setting the
productionMode
should be donevia vaadin extension:
Alse need to decide about which prefix to use
for each set of tasks:
hilla
for Hilla specifictasks e.g.
hillaGenerate
vs.vaadin
everywheree.g.
vaadinGenerate
,vaadinConfigure
, and etc.Part of vaadin/platform#4945