David Smiley

I'll come back to this today/tomorrow. I really appreciate the close look @stillalex :-) My biggest question is really scoping. This PR is a bit all over the place; it...

The elaborate caching configuration is not in Lucene, despite that same elaborate caching configuration being committed before the lucene-solr split. Thus Lucene devs removed it. In particular, it was @dweiss...

@madrob when you first added that 5 years ago, we weren't using the GHA gradle action or it didn't exist then. It now does with caching built-in. My goal here...

The docker build isn't taking any noticeably longer here than the test runs I see in the GHA dashboard for that script. I want to merge this Tuesday evening.

However it doesn't work because a conflict of Groovy transitive dependencies between this plugin and elsewhere in our build: ``` * What went wrong: A problem occurred configuring root project...

I added a gradle task that generates a change YAML. This is tailored for our project, pre-fills some things, and is overall less of a hassle that `logchange:add` is.

I think the plugin's generation of the YAML is too problematic and has too little value-add. This *draft* PR includes a task "generateChangeYaml" that generates it; we should use that...

Maybe the "add" feature of the logchange plugin is more useful to Maven. In Gradle, with native scripting, it was quite easy to tailor something specific to the project's needs.

> I do think there are things that Lucene can learn from JVector. It would be way better for the Lucene community as a whole to "do the hard thing"...

Non-default codecs don't have the high support burden that the default codec has, in terms of backwards compatibility and general documentation expectations. Few users will choose it. If we have...