[
https://issues.apache.org/jira/browse/LUCENE-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462159#comment-17462159
]
Dawid Weiss commented on LUCENE-10328:
--------------------------------------
I would rather fix the test framework to behave like a proper module... Then no
module patching is really necessary and things would work. I know what you mean
though and I'll take a look at it but I wouldn't want to increase the
complexity of this beyond what's really essential - the more module-related
arguments we have to use, the more of a headache it'll be for all the tasks and
tools we invoke.
> Module path for compiling and running tests is empty
> ----------------------------------------------------
>
> Key: LUCENE-10328
> URL: https://issues.apache.org/jira/browse/LUCENE-10328
> Project: Lucene - Core
> Issue Type: Sub-task
> Reporter: Dawid Weiss
> Priority: Major
> Attachments: image-2021-12-19-12-29-21-737.png
>
>
> Uwe noticed that the module path for compiling and running tests is empty -
> indeed, the modular configurations we create for the test sourceset do not
> inherit from their main counterparts. This is not a standard thing created
> for a sourceset - the test-main connection link is created by gradle's java
> plugin. We need to do a similar thing for modular configurations.
> !image-2021-12-19-12-29-21-737.png|width=490,height=280!
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
