Skip to content

Commit b013b61

Browse files
committed
Make JDK byte code verification bug workaround Java 8 compatible
A workaround for a JDK bug that affects PowerMock only work with Java 7. The -UseSplitVerifier option is no longer supported in Java 8. As an alternative workaround, this patch disables the byte code verifier entirely. Since this is only used with our own unit tests, the impact is low. Target: trunk Request: 2.10 Request: 2.9 Request: 2.8 Request: 2.7 Request: 2.6 Require-notes: no Requier-book: no Acked-by: Paul Millar <paul.millar@desy.de> Patch: https://rb.dcache.org/r/7197/ (cherry picked from commit d06ed79)
1 parent 85fa589 commit b013b61

File tree

1 file changed

+6
-5
lines changed

1 file changed

+6
-5
lines changed

pom.xml

Lines changed: 6 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -968,14 +968,15 @@
968968
to accept the overhead of forking each test run. -->
969969
<forkMode>always</forkMode>
970970

971-
<!-- OpenJDK v1.7.0_65 has a regression where the byte-code generated by
972-
powermock is not accepted. OpenJDK v1.7.0_60 and earlier are not
973-
affected by this problem. It is described here:
971+
<!-- JDK v1.7.0_65 and JDK 1.8.0_11 have a regression where the byte-code
972+
generated by powermock is not accepted. JDK v1.7.0_60 and earlier and
973+
1.8.0_5 and earlier are not affected by this problem. It is described here:
974974
975975
https://bugs.openjdk.java.net/browse/JDK-8051012
976976
977-
as a work-around, we disable the split verifier. -->
978-
<argLine>-XX:-UseSplitVerifier</argLine>
977+
As a work-around, we disable the verifier.
978+
-->
979+
<argLine>-noverify</argLine>
979980
</configuration>
980981
</plugin>
981982

0 commit comments

Comments
 (0)