On Tue, 22 Sep 2026 15:51:25 GMT, Andy Goryachev <[email protected]> wrote:
>> Yes, this will be going backwards. The external executions that Gradle can't >> follow mess up the caching. I recently added a [Gradle build >> file](https://github.com/nlisker/jfx/blob/9eaf738cc83a0d4ae845346efd8c5e8f3b510ec0/tests/performance/3DLighting/build.gradle) >> for the 3DLighting test application, and that one is external to the main >> build. Here we're wiring a new project to the main build, thus increasing >> the technical debt. > > I don't quite get this aversion to `ant`. This build file worked without > changes since probably 2014, yet with `gradle` we had to go through upgrades, > additional build steps... Gradle tries really hard to avoid doing work, which significantly speeds up repeated builds. But that only works if Gradle can precisely track the inputs and outputs of tasks, which it can't do if we're invoking another build system. ------------- PR Review Comment: https://git.openjdk.org/jfx/pull/2156#discussion_r4073711402
