Per [feature-requests:#1203], we are currently using a custom build of Lucene: lucene-core-5.2.1-SNAPSHOT.jar. Details from RFE:
- A few components within Lucene use features that are restricted when running under Java WebStart. This requires us to use a custom patched version.
When we are able to upgrade to a version of Lucene that is not affected by this issue, we should switch back to a standard build. This ticket should remain open until then.
Feature Requests: #1203
Feature Requests: #1299
Feature Requests: #1551
Our custom build is published on Bintray/JCenter for consumption as a Maven-style dependency:
https://bintray.com/omegat-org/maven/lucene-core
compile 'org.omegat.lucene:lucene-core:5.2.1'Last edit: Aaron Madlon-Kay 2016-10-31
The bug has been fixed in Lucene 6 and 7, but is unlikely to be backported to 5, much less 5.2, so we will have to continue to maintain our fork until LanguageTool upgrades to 6 or later.
LanguageTool 3.9 uses Lucene 5.5.4, in which this issue is fixed. We can stop using our fork when we are able to update to LanguageTool 3.9 or later (see [#1299]).
Related
Feature Requests: #1299
We dropped WebStart
OmegaT 6.1 also updates dependency to Lucene 5.5.5 and LanguageTool 5.7.