[
https://issues.apache.org/jira/browse/LUCENE-10561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17535830#comment-17535830
]
Robert Muir commented on LUCENE-10561:
--------------------------------------
Some of the tokenizers are auto-generated. For example ClassicTokenizerImpl is
generated by "jflex" tool from ClassicTokenizer.jflex sources.
The build is just failing because the wrong file was changed.
Personally I recommend avoiding ClasicTokenizerImpl or similar for this issue,
because these particular generated tokenizers are very complicated. It is hard
to reduce the member/class visibility due to the way the code generation works.
> Reduce class/member visibility of ArabicStemmer, ArabicNormalizer, and
> PersianNormalizer
> ----------------------------------------------------------------------------------------
>
> Key: LUCENE-10561
> URL: https://issues.apache.org/jira/browse/LUCENE-10561
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Tomoko Uchida
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is a spin-off of [LUCENE-10312].
> Constants and methods in those classes are exposed to the outside packages;
> we should be able to limit the visibility to {{private}} or, at least to
> {{package private}}.
> This change breaks backward compatibility so should be applied to the main
> branch (10.0) only, and a MIGRATE entry may be needed.
> Also, they seem unchanged since 2008, we could refactor them to embrace newer
> Java APIs as we did in [https://github.com/apache/lucene/pull/540].
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
