Lucene and Solr builds [LUCENE-4329]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
There are a raft of Perl scripts in the Lucene/Solr project. Five are used by the build, one is an undocumented release manager's tool, three are code generators that are saved for reference, and 2 appear truly dead.
```
lucene/benchmark/build.xml refers to scripts/shingle.bm2jira.pl
lucene/build.xml refers to @{changes.src.dir}/changes2html.pl
OR lucene/site/changes/changes2html.pl
lucene/common-build.xml refers to ${dev-tools.scripts.dir}/write.stage.maven.build.xml.pl
OR dev-tools/scripts/write.stage.maven.build.xml.pl
solr/build.xml refers to ${common-solr.dir}/dev-tools/stub-analysis-factory-maker.pl
OR solr/dev-tools/stub-analysis-factory-maker.pl
lucene/benchmark/build.xml refers to scripts/collation.bm2jira.pl
```
This is a release manager's tool which is not documented anywhere that LucidFind crawls: . Perhaps it should be added to the release manager's checklist?
```
dev-tools/scripts/poll-mirrors.pl
```
These appear to be standalone scripts that someone may want to run by hand:
```
lucene/analysis/common/src/test/org/apache/lucene/analysis/core/generateJavaUnicodeWordBreakTest.pl
lucene/benchmark/scripts/compare.collation.benchmark.tables.pl
lucene/benchmark/scripts/compare.shingle.benchmark.tables.pl
```
These appear to be assistants whose time is past.
```
dev-tools/scripts/LUCENE-3753.patch.hack.pl dates from 3.4 accd. to the CHANGES file.
dev-tools/scripts/LUCENE-3753.patch.hack.pl is from February 2012.
```
---
Migrated from [LUCENE-4329](https://issues.apache.org/jira/browse/LUCENE-4329) by Lance Norskog
Contributor guide
Research direction
Start by checking the listed lucene/benchmark/build.xml, lucene/build.xml, lucene/common-build.xml, solr/build.xml, and dev-tools/scripts/poll-mirrors.pl references. Review the named standalone scripts and the CHANGES history for LUCENE-3753.patch.hack.pl. Done means build-used scripts are accounted for, the release tool's documentation need is resolved, and obsolete scripts have an agreed disposition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- perl
- Domain
- build-system, tooling
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100