Illegal access with Java 9
See original GitHub issueWhen running with java 9 you get the following warning:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by khttp.requests.GenericRequest (file:/C:/Users/Torben/.m2/repository/khttp/khttp/0.1.0/khttp-0.1.0.jar) to field java.net.URL.host
WARNING: Please consider reporting this to the maintainers of khttp.requests.GenericRequest
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Issue Analytics
- State:
- Created 6 years ago
- Reactions:19
- Comments:16
Top Results From Across the Web
Java 9 Illegal Reflective Access Warning - Baeldung
Before Java 9, the Java Reflection API has a superpower: It could gain access to the non-public class members without limitation.
Read more >What is an illegal reflective access? - java - Stack Overflow
Run it with --illegal-access=deny to get to know about and avoid opening packages from one module to another without a module declaration ...
Read more >Java 9 Modules - The Unnamed Module and Accessing JDK ...
The default mode, --illegal-access=permit , is intended to make you aware of code on the class path that reflectively accesses any JDK-internal ...
Read more >Illegal access in Java 16 A.K.A. 'My program crashes!'
This means that if your application summons the demons of deep reflection, either in the code you & your team wrote, or in...
Read more >How to fix “an illegal reflective access operation has occurred”
The "an illegal reflective access operation has occurred" warning message is related to the unauthorized access to parts of the JDK made by ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well either we can count this project as dead (what are the alternatives) or fix it.
I’m happy to look at trying to do the fix, and fix the build whilst I’m at it, though that may involve a migration to Gradle Kotlin DSL whilst I’m at it.
Are people still interested in the fix?
3 years after reported and the last comment is “it would be nice to fix this”, this is no bueno