apache/lucene-solr: the shared repository that stopped holding code
Apache Lucene and Solr open-source search software
At a glance
- What is it?
- The GitHub repository that once carried both search engines now carries neither, only a pointer to two separate clones and one leftover bugfix branch. Anyone cloning it for a tutorial or a dependency will find almost nothing to build.
- Who is it for?
- Adopt neither project from this repository. Clone the Lucene or Solr mirror on GitHub directly if you are building on one of them, and treat branch_8_11 as the only line still taking fixes here.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- apache/lucene-solr4,365 ★ · -1
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| apache/lucene-solr | 4.4k | 4.4k |
-1 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The repository is a signpost with four files at the top level
Clone this repository today and the whole file listing fits on one screen. That is the entire top level. No source tree, no build script, no distribution.
This matters because the repository name still travels under both projects at once. Solr became a top-level ASF project, and main line development for Lucene and Solr moved into each project's own git repository. The shared history stayed behind as a record of where the code used to live.
The audience for that fact is narrow and specific: engineers who found an old clone path, a CI recipe, a tutorial or a build script that still targets this repository, and who now get an empty build and no error explaining why. The licence is Apache-2.0 and the repository is not archived. The last push was on 2026-05-15.
Two clone URLs replace the shared one
The README gives the split as two git remotes on GitBox, one at repos/asf/lucene.git and one at repos/asf/solr.git. Those are the two trees where current work happens.
If your local remote list still names the shared repository, fetching from it gets you none of the main line development after the split, which happens in the other two clones, apart from 8.11.x bugfixes on branch_8_11, so a self-hosted mirror or an air-gapped build that only knows this URL will silently fall behind without any error.
There is a second layer for GitHub users. The README points at the corresponding repository mirror for each project, and asks that pull requests be created against the main branch there. So the answer to "where do I send a patch" and the answer to "where do I pull the source" point at the same pair of mirrors, which is at least one less thing to get wrong than when a single repository served both purposes.
branch_8_11 is the last branch here that still takes fixes
One thing still moves in this repository: bugfixes for the 8.11.x line stay on branch_8_11, and the README keeps the shared clone URL alive for that reason.
Read that narrowly. It covers bugfix work on one old line. It is not an open development line, it does not carry the current Solr or Lucene tree, and the README does not say when it will close or where those fixes get merged back. Anyone still on 8.11.x is working against a frozen branch with a narrow backport policy, not against the moving main line.
There is also a naming catch worth stating plainly. The default branch of this repository is master, and a file listing that shows master next to a nearly empty tree is the expected state after the split, not a broken checkout or a truncated clone.
Fork pull requests land on each project's main branch
GitHub is treated as a mirror plus a contribution surface, not as the source of truth. The README asks for a clone of the corresponding mirror and a pull request against its main branch.
Two consequences follow. Anyone automating contributions has to change its remote and its target branch at the same time, which is exactly the sort of change that gets half done and left pointing at the shared repository.
PRs.md also sits at the top level of this repo.
There is no install command here, so start from the homepage
The README contains no install step, no build invocation and no example query, so there is nothing to copy into a terminal. The repository's homepage is lucene.apache.org, and that is where an engineer who wants to run either engine should start.
The practical sequence is short: decide which of the two projects you need, clone that project's own repository rather than this one, and take build and configuration instructions from that site. If a tutorial, a Docker image reference or a dependency declaration still points at the old shared clone path, treat it as stale.
Why this repository cannot settle the Lucene or Solr question
This repository gives you no comparison between the two. It contains no design notes, no API surface, no feature matrix and no migration guidance. Its only claim is administrative: two projects, two repositories.
Where an alternative helps: a maintained open source search engine that wraps the same Lucene indexing core and ships its own distribution, JVM, configuration and HTTP interface. That is a different approach, embedding the library inside a service rather than wiring the library into your own application code. Judging between the two means reading each project's own documentation, not this pointer file.
What the file listing says that the prose does not
Count the entries. Four top level items, one of them a contribution note, one a GitHub configuration directory, and one the file you have just read. Nothing else ships.
An engineer evaluating a dependency by cloning it and reading what ships would score this repository at zero, correctly. What it still holds is traceability: the exact moment the two projects separated, and where the maintenance tail of 8.11.x lives, which is harder to reconstruct once old clones disappear.
Keep one copy of that pointer if you maintain scripts that resolve search dependencies, and otherwise let your tooling skip it entirely.
Editorial conclusion
Adopt neither project from this repository. Clone the Lucene or Solr mirror on GitHub directly if you are building on one of them, and treat branch_8_11 as the only line still taking fixes here. Do not pick this repo as a dependency source, a CI cache, or a way to answer the Lucene or Solr question, because its top level holds four files and no build script. The one thing to verify first is whether the branch you clone actually carries source: on the default branch of this repository it does not, and on branch_8_11 you get an old bugfix line, nothing newer. Read the project homepage, lucene.apache.org, before writing any build step that depends on either engine.
Frequently asked questions
Which is better: Lucene or Solr?
This repository does not answer that. Its README records only that Solr became a top-level Apache project and that main line development for both moved into each project's own git repository, with bugfixes for 8.11.x remaining on branch_8_11 here.
Is Solr still relevant?
The README states that Solr has become a top-level Apache project and that its main line development now happens in its own repository at gitbox.apache.org/repos/asf/solr.git. The repository gives no roadmap, version policy or adoption figures.
Is Apache Lucene still used?
The one trace of ongoing work here is bugfix development for the 8.11.x line, which remains on branch_8_11 in this shared repository. Current Lucene work lives in gitbox.apache.org/repos/asf/lucene.git.
What are the key differences between Apache Lucene and Solr?
The only difference this repository states is administrative: they are separate top-level Apache projects with separate git repositories and separate main lines. It documents no API, packaging or configuration differences between them.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/apache-lucene-solr)Star history chart for your README
[](https://hysenlabs.com/projects/apache-lucene-solr)Was this useful?