[
https://issues.apache.org/jira/browse/LUCENE-10261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449036#comment-17449036
]
Dawid Weiss commented on LUCENE-10261:
--------------------------------------
I have an interesting question. If you build Luke in stand-alone mode (or a
release, doesn't matter) then this does scan packages (and display analyzers)
correctly on the PR branch for LUCENE-10260:
{code}
gradlew -p lucene/luke standaloneAssemble
java --module-path lucene/luke/build/lucene-luke-10.0.0-SNAPSHOT --add-modules
org.apache.logging.log4j -m lucene.luke
{code}
but if you go back to main, recompile, then it goes back to StandardAnalyzer
only...
Really, I'm not kidding. Try it.
The only difference is that I removed LucenePackage (and moved the impl.
version method to Version). I think it's a quirk in the module system somewhere
but it's something truly bizarre. That hack with JAR scanning based on
directory resource URLs is really fragile nonetheless as JARs (ZIPs) don't need
to have any directory entries at all (just files) - that they do have directory
entries is just a happy coincidence.
> Preset/ custom analyzer pipelines in Luke won't work with the module system
> ---------------------------------------------------------------------------
>
> Key: LUCENE-10261
> URL: https://issues.apache.org/jira/browse/LUCENE-10261
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Dawid Weiss
> Priority: Major
>
> A spinoff from LUCENE-10255
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
