Laird Nelson created SUREFIRE-1605:
--------------------------------------
Summary: NoClassDefFoundError (RunNotifier) with JDK 11
Key: SUREFIRE-1605
URL: https://issues.apache.org/jira/browse/SUREFIRE-1605
Project: Maven Surefire
Issue Type: Bug
Components: Junit 4.x support, Maven Surefire Plugin
Affects Versions: 3.0.0-M1
Reporter: Laird Nelson
I have a JUnit 4 test. JUnit 4.12 is on the test classpath. I'm using JDK 11
via toolchains and the Surefire plugin version 3.0.0-M1.
{{mvn test}} fails with the following dump indicating that JDK 11's
{{jdk.internal.loader.BuiltinClassLoader}} cannot find the JUnit 4 class
{{org.junit.runner.notification.RunNotifier}} class:
{code:java}
# Created at 2018-11-30T14:30:40.517
java.lang.NoClassDefFoundError: org/junit/runner/notification/RunNotifier
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at java.base/java.lang.Class.privateGetDeclaredConstructors(Class.java:3138)
at java.base/java.lang.Class.getConstructor0(Class.java:3343)
at java.base/java.lang.Class.getConstructor(Class.java:2152)
at
org.apache.maven.surefire.util.ReflectionUtils.getConstructor(ReflectionUtils.java:83)
at
org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:122)
at
org.apache.maven.surefire.booter.ForkedBooter.createProviderInCurrentClassloader(ForkedBooter.java:403)
at
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
at
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:345)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:126)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:418)
Caused by: java.lang.ClassNotFoundException:
org.junit.runner.notification.RunNotifier
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
... 11 more{code}
I see no workaround.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
