Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
9.1
-
None
-
New
Description
When we refactored the constructors for these resource objects used by the kuromoji JapaneseTokenizer, we (inadvertently, I expect) changed the behavior for consumers that were supplying these resources on the classpath. In that case, we silently replaced the custom resources with the Lucene built-in ones. I think we cannot support the old API because of Java Module system restrictions, but we didn't provide any usable replacement or notice either.
This issue is for exposing the new (private) constructors that accept streams, and adding a notice to Migration.md to point users at them, since they can be used with resources streams loaded from the classpath by the caller.
