You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version of JMockit that was used:
-- JMockit 1.49
-- JaCoCo 0.8.3 (newer versions as 0.8.8 are not working with JMockit)
-- Gradle 7.4.2
-- Java 17
Description of the problem or enhancement request:
JaCoCo causes Stacktraces when runing the project with Java 17. Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 61
This would be solved in newer JaCoCo versions, but those are not compatilbe with JMockit due to condy properly... See:conflict with jmockit on java 11 jacoco/jacoco#896
Run gradlew clean build for the attached sample project and see console output...
Check the following:
If a defect or unexpected result, JMockit project members should be able to reproduce it.
For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which
can be executed without changes and reproduces the failure. jmockit_jacoco.zip
If an enhancement or new feature request, it should be justified by an example test
demonstrating the validity and usefulness of the desired enhancement or new feature.
The issue does not fall outside the scope of the project (for example, attempting to use
JMockit APIs from Groovy or Scala code, or with an Android runtime).
The JDK where the problem occurs is a final release, not a development build.
Please provide the following information:
Version of JMockit that was used:
-- JMockit 1.49
-- JaCoCo 0.8.3 (newer versions as 0.8.8 are not working with JMockit)
-- Gradle 7.4.2
-- Java 17
Description of the problem or enhancement request:
JaCoCo causes Stacktraces when runing the project with Java 17.
Caused by: java.lang.IllegalArgumentException: Unsupported class file major version 61This would be solved in newer JaCoCo versions, but those are not compatilbe with JMockit due to condy properly... See: conflict with jmockit on java 11 jacoco/jacoco#896
Run
gradlew clean buildfor the attached sample project and see console output...If a defect or unexpected result, JMockit project members should be able to reproduce it.
For that, include an example test (perhaps accompanied by a Maven/Gradle build script) which
can be executed without changes and reproduces the failure.
jmockit_jacoco.zip
If an enhancement or new feature request, it should be justified by an example test
demonstrating the validity and usefulness of the desired enhancement or new feature.
The issue does not fall outside the scope of the project (for example, attempting to use
JMockit APIs from Groovy or Scala code, or with an Android runtime).
The JDK where the problem occurs is a final release, not a development build.