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

GenerateJavaTask is difficult for gradle to cache #513

Open
simongellis-attentive opened this issue Jan 17, 2023 · 0 comments
Open

GenerateJavaTask is difficult for gradle to cache #513

simongellis-attentive opened this issue Jan 17, 2023 · 0 comments

Comments

@simongellis-attentive
Copy link

Hello!

My company is trying to optimize our gradle caching, and it looks like the DGS GenerateJavaTask is causing a bit of trouble. Specifically, the generateSourcesDir input is a String containing an absolute filepath, which seems to foil remote caching attempts (since repos are cloned to different locations on different machines). Gradle can cache paths well if they're annotated with @PathSensitive(PathSensitivity.RELATIVE), but I'm not sure whether that works on string properties.

I think that PR #356 would allow us to work around this; it'd let us assign specific values to the output dirs, so we could set generatedSourcesDir to some stable empty string and it'd stop busting the cache. Is that PR likely to be merged at some point?

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

No branches or pull requests

1 participant