[LUCENE-9134] Port ant-regenerate tasks to Gradle build

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 9.0
• Lucene Fields: New
• Assignee: Erick Erickson
• Reporter: Erick Erickson
• Created: 14/Jan/20 01:22
• Updated: 28/Aug/22 15:55
• Resolved: 11/Feb/20 23:58

Description

Take II about organizing this beast.
A list of items that needs to be added or requires work. If you'd like to work on any of these, please add your name to the list. See process comments at parent (LUCENE-9077)

• Implement jflex task in lucene/core
• Implement jflex tasks in lucene/analysis
• Implement javacc tasks in lucene/queryparser (EOE)
• Implement javacc tasks in solr/core (EOE)
• Implement python tasks in lucene (? there are several javadocs mentions in the build.xml, this may be irrelevant to the Gradle effort).
• Implement python tasks in lucene/core
• Implement python tasks in lucene/analysis

 

Here are the "regenerate" targets I found in the ant version. There are a couple that I don't have evidence for or against being rebuilt

 // Very top level

./build.xml: <target name="regenerate" description="Runs all code regenerators">
./build.xml: <subant target="regenerate" inheritall="false" failonerror="true">
./build.xml: <target name="regenerateAndCheck" depends="regenerate,-check-after-regeneration"/>
 

// top level Lucene. This includes the core/build.xml and test-framework/build.xml files

./lucene/build.xml: <target name="regenerate">
./lucene/build.xml: <subant target="regenerate" failonerror="true" inheritall="false">
./lucene/build.xml: <modules-crawl target="regenerate"/>
 

// This one has quite a number of customizations to

./lucene/core/build.xml: <target name="regenerate" depends="createLevAutomata,createPackedIntSources,jflex"/>
 

// This one has a bunch of code modifications after javacc is run on certain of the
// output files. Save this one for last?

./lucene/queryparser/build.xml: <target name="regenerate" depends="javacc"/>
 

// the files under ../lucene/analysis... are pretty self contained. I expect these could be done as a unit

./lucene/analysis/build.xml: <target name="regenerate">
./lucene/analysis/build.xml: <forall-analyzers target="regenerate"/>

./lucene/analysis/common/build.xml: <target name="regenerate" depends="jflex,unicode-data"/>
./lucene/analysis/icu/build.xml: <target name="regenerate" depends="gen-utr30-data-files,gennorm2,genrbbi"/>
./lucene/analysis/kuromoji/build.xml: <target name="regenerate" depends="build-dict"/>
./lucene/analysis/nori/build.xml: <target name="regenerate" depends="build-dict"/>
./lucene/analysis/opennlp/build.xml: <target name="regenerate" depends="train-test-models"/>
 

 

// These are regenerated from the top-level regenerate target, but for –

LUCENE-9080//the changes were only in imports so there are no

//corresponding files checked in in that JIRA

./lucene/expressions/build.xml: <target name="regenerate" depends="run-antlr"/>
 

// Apparently unrelated to ./lucene/analysis/opennlp/build.xml "train-test-models" target

// Apparently not rebuilt from the top level, but are regenerated when executed from

// ./solr/contrib/langid

./solr/contrib/langid/build.xml: <target name="regenerate" depends="train-test-models"/>
 

 

Issue Links

• is depended upon by: LUCENE-9151 Get lint and deprecation warnings out of lucene/queryparsers
• links to: GitHub Pull Request #1230
• links to: GitHub Pull Request #1251