[
https://issues.apache.org/jira/browse/LUCENE-10338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17465408#comment-17465408
]
ASF subversion and git services commented on LUCENE-10338:
----------------------------------------------------------
Commit aab0413b5700a833339e2532a700d1bd29c19282 in lucene's branch
refs/heads/branch_9x from Dawid Weiss
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=aab0413 ]
LUCENE-10338: Scan for tests only by convention file name pattern (#565)
> Scan for tests only by convention file name pattern (Test*)
> -----------------------------------------------------------
>
> Key: LUCENE-10338
> URL: https://issues.apache.org/jira/browse/LUCENE-10338
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Dawid Weiss
> Assignee: Dawid Weiss
> Priority: Trivial
> Fix For: 9.1
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> Gradle is smart by trying to figure out which class is a JUnit test and which
> isn't. This works only to certain limits - as Uwe pointed out, when the
> runtime JDK is newer than gradle, the bytecode cannot be parsed and the
> detection fails. Tests under the module system are also affected by this
> "scanning".
> Since we enforce test class names anyway, I think we can scan for tests by
> file name rather than using this gradle feature.
> Patch coming.
--
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
