make all of lucene modules lucene-contrib.jar in 6.0 [LUCENE-6573]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
When we added modules, there was a big effort to make sure that there was not stupid dependencies between them. I remember spending a lot of time adding components like MockAnalyzer and switching all tests over to them so that this could be successful.
Despite that work, people just CANT RESIST DOING THIS but it makes things impossible to use. So I'd rather just make a big lucene-contrib.jar, since folks are unable to be mature about it.
---
Migrated from [LUCENE-6573](https://issues.apache.org/jira/browse/LUCENE-6573) by Robert Muir (@rmuir), updated Jun 24 2015
Attachments: [LUCENE-6573.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-6573/LUCENE-6573.patch)
Contributor guide
Research direction
Start with the migrated LUCENE-6573 issue and its attached LUCENE-6573.patch, then inspect the module and build configuration they identify. Determine how all modules should be packaged into lucene-contrib.jar while preserving the stated dependency goal; done means the requested aggregate artifact builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, build-system
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100