You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Tomoko Uchida (Jira)" <ji...@apache.org> on 2022/04/01 06:29:00 UTC

[jira] [Resolved] (LUCENE-10485) Limit o.a.l.a.morph package visibility only to kuromoji and nori

     [ https://issues.apache.org/jira/browse/LUCENE-10485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomoko Uchida resolved LUCENE-10485.
------------------------------------
    Resolution: Won't Fix

I'm closing this (at this moment).

Instead of trying to hide the `o.a.l.a.morph` package from 3rd party modules, I'll try to polish it so that we can publish it as a first-class citizen of the analysis-common module.

> Limit o.a.l.a.morph package visibility only to kuromoji and nori
> ----------------------------------------------------------------
>
>                 Key: LUCENE-10485
>                 URL: https://issues.apache.org/jira/browse/LUCENE-10485
>             Project: Lucene - Core
>          Issue Type: Task
>            Reporter: Tomoko Uchida
>            Priority: Minor
>         Attachments: hacky-poc-make-kuromoji-test-named-module.patch
>
>
> LUCENE-10393 added a new package {{org.apache.lucene.analysis.morph}} to analysis-common that is supposed to be used by only analysis-kuromoji and analysis-nori modules. It would be better to reduce its visibility (on module-mode) by "export to" clause in the module descriptor. 
> The major issue here may be unit tests. They also have to be converted to properly named modules otherwise they cannot access the {{o.a.l.a.morph}} package.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org