Powermock Compatibility with JDK 17

Question

Recently I was upgrading my project from JDK 11 to JDK 17. After upgrading, powermock seems to have an issue. While running AUT's , I am getting following error:

java.lang.RuntimeException: PowerMock internal error: Should never throw exception at this level
Caused by: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not "opens java.lang" to unnamed module @3fc34119

Do you know any workaround this issue, If so can you please provide the solution.

Have you taken a look if there are newer versions of powermockito that might be required for more recent versions of java? — f1sh, Nov 09 '21 at 10:05
Could it be that you encountered open issue [1099](https://github.com/powermock/powermock/issues/1099) and/or [1094](https://github.com/powermock/powermock/issues/1094)? — Hulk, Nov 09 '21 at 10:29
If you want to stay up-to-date with recent JDK versions, I suggest to stay with mockito. Historically, Powermock has taken longer time to keep up, while mockito has a bigger ecosystem around it, both in terms of users and developers. — gjoranv, Nov 09 '21 at 13:44
After encountering this incompatibility once again, I've used it as an opportunity to review whether I truly needed Powermock. In my case, I was only using it for mocking static classes, which is since supported in Mockito. — Paul Lammertsma, Mar 26 '23 at 15:51

score 17 · Answer 1 · edited Feb 25 '22 at 11:08

17

As a stop gap measure (until Powermock gets updated), you should be able to run your tests by passing the following argument to your JVM:

--add-opens java.base/java.lang=ALL-UNNAMED

If you're running your tests with Maven, you can configure the surefire-plugin like this:

<plugin>
  <artifactId>maven-surefire-plugin</artifactId>
  <version>${plugin.surefire.version}</version>
  <configuration>
    <argLine>--add-opens java.base/java.lang=ALL-UNNAMED</argLine>
  </configuration>
</plugin>

edited Feb 25 '22 at 11:08

Sadra

2,480
2
20
32

answered Feb 21 '22 at 08:47

julmud

171
1
3
7

2

Also you can use these: --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.io=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.base=ALL-UNNAMED – Efecan AHMETOĞLU Apr 20 '22 at 07:46
1

Worked for me (JDK 17) – Roy Wasse Apr 27 '22 at 18:50
how to use it in gradle? – Imtiaz Ali Jan 17 '23 at 12:04
1

@ImtiazAli this worked for me: test { jvmArgs "--add-opens", "java.base/java.lang=ALL-UNNAMED" } – Vladimir Atanasov Mar 07 '23 at 16:20
2

How to make this work in case I want to run the tests in Intellij? In other words, if I right click on the test class, then I click run, it will still throw the exception mentioned above. – MA1 May 03 '23 at 18:28
@MA1 If you re using gradle check my answer. – mbwasi May 16 '23 at 21:59

score 3 · Answer 2 · answered May 16 '23 at 21:58

This shoudl allow the solution to work with tests ran from inside the IDE, Android Studio in my case.

I had to do this because PowerMock doesn't play nice with Java 17 on Android.

In your top level project build.gradle, at the bottom just add

subprojects{
    tasks.withType(Test).configureEach{
        jvmArgs = jvmArgs + ['--add-opens=java.base/java.lang=ALL-UNNAMED']
    }
}

If you are using Kotlin for your Gradle files see https://github.com/square/okhttp/blob/f9901627431be098ad73abd725fbb3738747461c/build.gradle.kts#L153

this is a great answer, it fixed Android Studio and my failing Jenkins build! — Greg Moens, Aug 07 '23 at 20:15

Powermock Compatibility with JDK 17

2 Answers2