Open martin-walsh opened 1 year ago
Opening this PR as a conversation starter around support for new --configuration-cache flag in Gradle.
--configuration-cache
Essentially, if a project uses any plugins which do not defer creation of Tasks, a user cannot make use of configuration cache.
The main changes required are to use the lazy init apis i.e. register vs create & named vs findByName.
register
create
named
findByName
The code looks like it requires more changes than I have made here so far, but before I do so, it's best to discuss.
See:
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅
I have read the CLA Document and I hereby sign the CLA
recheck
@yahavi How can I start a discussion on this ?
Opening this PR as a conversation starter around support for new
--configuration-cache
flag in Gradle.Essentially, if a project uses any plugins which do not defer creation of Tasks, a user cannot make use of configuration cache.
The main changes required are to use the lazy init apis i.e.
register
vscreate
&named
vsfindByName
.The code looks like it requires more changes than I have made here so far, but before I do so, it's best to discuss.
See: