[
https://issues.apache.org/jira/browse/SUREFIRE-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated SUREFIRE-2268:
------------------------------------------
Fix Version/s: 3.5.1
> Tests run under classpath if JDK 23 is used
> -------------------------------------------
>
> Key: SUREFIRE-2268
> URL: https://issues.apache.org/jira/browse/SUREFIRE-2268
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
> Affects Versions: 3.5.0
> Reporter: Gili
> Priority: Major
> Fix For: 3.5.1
>
>
> Something odd is going on with JDK 23. If I run my tests under JDK 21 or JDK
> 22 they run under the module-path. If I change "maven.compiler.release" to
> 23, then all of a sudden Surefire is running the tests on the classpath. It's
> odd. I'm not changing anything else about my code. If I run:
>
> LoggerFactory.getLogger(getClass()).info("class: {}, module: {}", getClass(),
> getClass().getModule().toString());
>
> under JDK 21, I get a module name. Under JDK 23, I get "unnamed module" and
> module-specific functionality breaks (e.g. Module.getDescriptor() returns
> null).
>
> Have you tried running any of the integration tests under JDK 23? I'm hoping
> you can reproduce the problem on your end...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
