Apache Lucene open-source search software
Go to file
Peter Gromov cdff0accaa
Hunspell suggestions: speed up for some non-Latin scripts (#19)
2021-03-15 05:02:45 -04:00
.github Cleanup readme file, doaps and copy build instructions from lucene subfolder (#6) 2021-03-10 16:10:06 +01:00
.muse SOLR-14883 Add a Muse (Continuous assurance platform) configuration (#1901) 2020-09-23 17:42:19 -07:00
buildSrc LUCENE-9266 remove gradle wrapper jar from source 2020-04-02 11:30:01 -05:00
dev-docs SOLR-15160 update cloud.sh (#2393) 2021-02-21 14:36:19 -05:00
dev-tools Cleanup readme file, doaps and copy build instructions from lucene subfolder (#6) 2021-03-10 16:10:06 +01:00
gradle Flush output on javadoc emitting a failure. 2021-03-12 11:39:40 +01:00
help SOLR-15075: Solr docker gradle improvements (#2197) 2021-01-26 10:22:50 -05:00
lucene Hunspell suggestions: speed up for some non-Latin scripts (#19) 2021-03-15 05:02:45 -04:00
.asf.yaml titles for github 2021-03-10 12:51:06 +01:00
.dir-locals.el LUCENE-9322: Add Lucene90 codec, including VectorFormat 2020-10-18 07:49:36 -04:00
.git-blame-ignore-revs LUCENE-9570: code reformatting [record rev]. 2021-01-05 13:44:42 +01:00
.gitattributes LUCENE-9077: make git always keep .gradle files with LF EOLs. 2020-04-09 13:55:16 +02:00
.gitignore .gitignore clean up (#1993) 2020-10-24 11:09:55 -04:00
.hgignore
LICENSE LUCENE-9233 Add top level LICENSE file 2020-02-20 20:53:57 +01:00
README.md Fix badge URL after Jenkins job rename 2021-03-10 23:52:29 +01:00
build.gradle LUCENE-9375: some build file cleanups. (#10) 2021-03-10 21:47:37 +01:00
gradlew Gradle hotfix in preparation for Jenkins: Fix for whitespace in directory violations 2020-08-23 17:51:11 +02:00
gradlew.bat Gradle hotfix in preparation for Jenkins: Fix for whitespace in directory violations 2020-08-23 17:51:11 +02:00
settings.gradle Cleanup readme file, doaps and copy build instructions from lucene subfolder (#6) 2021-03-10 16:10:06 +01:00
versions.lock LUCENE-9375: post-repo-split removal of solr counterpart. 2021-03-10 11:20:08 +01:00
versions.props LUCENE-9375: post-repo-split removal of solr counterpart. 2021-03-10 11:20:08 +01:00

README.md

Apache Lucene

Lucene Logo

Apache Lucene is a high-performance, full featured text search engine library written in Java.

Build Status

Online Documentation

This README file only contains basic setup instructions. For more comprehensive documentation, visit:

Building with Gradle

Basic steps:

  1. Install OpenJDK 11 (or greater)
  2. Download Lucene from Apache and unpack it
  3. Connect to the top-level of your installation (parent of the lucene top-level directory)
  4. Run gradle

Step 0) Set up your development environment (OpenJDK 11 or greater)

We'll assume that you know how to get and set up the JDK - if you don't, then we suggest starting at https://www.oracle.com/java/ and learning more about Java, before returning to this README. Lucene runs with Java 11 and later.

Lucene uses Gradle for build control.

NOTE: Lucene changed from Ant to Gradle as of release 9.0. Prior releases still use Ant.

Step 1) Checkout/Download Lucene source code

We'll assume you already did this, or you wouldn't be reading this file. However, you might have received this file by some alternate route, or you might have an incomplete copy of the Lucene, so: you can directly checkout the source code from GitHub:

https://github.com/apache/lucene

Or Lucene source archives at particlar releases are available as part of Lucene downloads:

https://lucene.apache.org/core/downloads.html

Download either a zip or a tarred/gzipped version of the archive, and uncompress it into a directory of your choice.

Step 2) Change directory (cd) into the top-level directory of the source tree

The parent directory for Lucene contains the base configuration file for the build. By default, you do not need to change any of the settings in this file, but you do need to run Gradle from this location so it knows where to find the necessary configurations.

Step 3) Run Gradle

Assuming you can exectue "./gradlew help" should show you the main tasks that can be executed to show help sub-topics.

If you want to build Lucene, type:

./gradlew assemble

NOTE: DO NOT use gradle command that is already installed on your machine (unless you know what you'll do). The "gradle wrapper" (gradlew) does the job - downloads the correct version of it, setups necessary configurations.

The first time you run Gradle, it will create a file "gradle.properties" that contains machine-specific settings. Normally you can use this file as-is, but it can be modified if necessary.

./gradlew check will assemble Lucene and run all validation tasks unit tests.

./gradlew help will print a list of help commands for high-level tasks. One of these is helpAnt that shows the gradle tasks corresponding to ant targets you may be familiar with.

If you want to build the documentation, type:

./gradlew documentation

Gradle build and IDE support

  • IntelliJ - IntelliJ idea can import the project out of the box. Code formatting conventions should be manually adjusted.
  • Eclipse - Not tested.
  • Netbeans - Not tested.

Contributing

Please review the Contributing to Lucene Guide for information on contributing.

Discussion and Support