You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 2, 2026. It is now read-only.
The Gradle JavaCompile task is leveraging the worker API and as such has ~/.gradle/workers as working directory.
It means that in the task context a relative path can't be used to retrieve resources like stubs for instance.
It is obviously possible to fallback to an absolute path location using ${project.rootdir}/stubs-example-folder but this has a negative impact on build caching as the task inputs can't be relocated. This means that you would only get a build cache hit when the project is built from the same location.
see this section of the Gradle documentation to get more details.
Potential fix:
Add the project directory as an internal input and use it as a prefix in the path if relative
Issue
The Gradle
JavaCompiletask is leveraging the worker API and as such has~/.gradle/workersas working directory.It means that in the task context a relative path can't be used to retrieve resources like
stubsfor instance.It is obviously possible to fallback to an absolute path location using
${project.rootdir}/stubs-example-folderbut this has a negative impact on build caching as the task inputs can't be relocated. This means that you would only get a build cache hit when the project is built from the same location.see this section of the Gradle documentation to get more details.
Potential fix:
Add the project directory as an internal input and use it as a prefix in the path if relative