Plugin Service Registration

[beatrizsanchez (Betty Sanchez)]

@st_oehme

You would have a getter annotated with @InputFiles and compute the actual set of files in there.

beatrizsanchez:

Thanks! Makes sense. I have tried this and works perfectly.

@st_oehme

If you really wanted this then instead of using @InputFiles , you’d have a getter returning a List<Long> (the timestamps of the files), annotated with @Input

This is a good idea as well. Thanks!

@st_oehme

I’d strongly discourage that, as it defeats any kind of correctness guarantee and may leave your users frustrated with wrong results.

I understand this would be problematic for the user if it was hardcoded in the plugin though I guess for some scenarios it might be useful. To deal with the this I was thinking on providing some sort of up-to-date validation task/extension that the code generation task needs to call and determine its validity based on the user-selected up-to-date criteria selected by the user.

I am thinking of a case where instead of changes in a file we need to poll for changes on a database based on a specific query or a global property that determines the database has been updated. It is not straight forward how to determine that it has been updated therefore we need more flexibility at the user’s discretion to define out-dated checks/stamps relevant for their workflow.