[
https://issues.apache.org/jira/browse/LUCENE-10328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17462785#comment-17462785
]
Dawid Weiss commented on LUCENE-10328:
--------------------------------------
There is another piece to the complexity which is currently not correct. Gradle
has separate "output" folders for classes and resources of a source set. We're
currently trying to optimize the compilation by taking the classes output but
this isn't sufficient for tests, for example, because we need a fully assembled
module (with resources!) for runtime execution. The module can't be split into
two folders for that.
It's related so I'll try to fix both as part of this issue.
> Module path for compiling and running tests is wrong
> ----------------------------------------------------
>
> 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
