Btw. this is a placeholder for some of the known bits that require solving.
https://issues.apache.org/jira/browse/LUCENE-9871 It'd be awesome to see some help from you guys at Gradle to solve the non-trivial things: - test runner and early/ internal JVM output (the issue I mentioned before), - test runner test case ordering optimization (load balancing between worker JVMs); currently the long-tail test case can slow down builds significantly. - support for user-local gradle.properties or computed properties there (we currently generate this file because it'll be slightly different for every developer, this requires a non-optimal first run), - support for project-controlled up-to-date mechanism (versioned artifact checksums) that is not bypassed on the first run. This is needed for generated resources - I didn't figure out how to do it other than with ugly hacks. If any of these is of interest to you, I can provide more pointers, of course. Let me know! Dawid On Wed, Oct 20, 2021 at 1:48 PM Jerome Prinet <[email protected]> wrote: > Hi Lucene team! > I am a software engineer at Gradle and I'd like to help you optimize > Lucene's Gradle build. > I have already been working on this topic and I'd like to open a PR. > Should I start by creating a JIRA issue first? > Please let me know how to proceed. > Kind regards, > > -- > > Jerome Prinet > Senior Software Engineer > Gradle > W. gradle.com > >
