Louis Jacomet
Louis Jacomet
No longer possible to specify a executable which is not part of a Java toolchain for a JavaExec task
Given: * #23990 * #24014 Could you see if the setup done for allowing ecj as a Java compiler can be used in your case?
No longer possible to specify a executable which is not part of a Java toolchain for a JavaExec task
Thank you for your interest in Gradle! This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.
The issue is in the backlog of the relevant team and is prioritized by them.
Thanks for taking the time to craft that answer. Like I said, I am fine with the current behavior of `set(Provider)` being the reference. I disagree with the current behavior...
This feature request is in the backlog of the relevant team and is prioritized by them. *** > Sure, if you tell me what was added for this. Without the...
We don't automatically include regressions in release notes. But they seem to be something about which we should make a decision case by case. I think that with the upcoming...
Are you able to exclude elements from the backup? As indicated early on in the path, those are `caches` and are not worth backing up.
This is the intended behavior, and there’s no plan to change it. This issue will be closed. *** The names and paths of these files in Gradle will remain unchanged....
We will take this over, but we have no ETA for properly validating this. Regarding gitstream: it can be ignored. No idea why that run does not stop and no...
Also to be clear, you did not miss anything as Gradle effectively disable these loggers.