[
https://issues.apache.org/jira/browse/LUCENE-10301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17464394#comment-17464394
]
Tomoko Uchida commented on LUCENE-10301:
----------------------------------------
The test-framework module has several service providers (codecs) for testing.
When it is placed in the module path, lucene-core tries to consume the services
when starting a Java application on module mode; this prevents from starting
the Luke app on the binary distribution since it cannot be resolved on that (we
won't re-distribute dependencies of test-framework, junit, etc.)
I opened a PR to place test-framework module into a separate modules folder. It
is actually just a partial revert on the previous commit.
https://github.com/apache/lucene/pull/566
> The test-framework as a module (or a separate test-framework-module)
> --------------------------------------------------------------------
>
> Key: LUCENE-10301
> URL: https://issues.apache.org/jira/browse/LUCENE-10301
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Major
> Fix For: 9.1
>
> Time Spent: 7h 40m
> Remaining Estimate: 0h
>
> The test framework has split packages. It's a follow-up to introducing
> modules but eventually the modular test subprojects will need something like
> the test framework too.
> I'm not sure whether we should start a new subproject for this or try to
> refactor the test framework, but it's a follow-up once the modules themselves
> are working and testable, I think.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
