WARNING: An illegal reflective access operation has occurred #5221
Replies: 1 comment
-
|
Hi @kmanikanta335, Could you share the version of Java you are using? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Operating System
windows 11
Android Studio Version
Android Studio Flamingo | 2022.2.1 Patch 1
RAM size
8 gb
Free disk space
240 gb
Which step are you stuck on?
this error while building the project in WSL using BAZEL
the error was encountered while following this path
command used : bazel build //:oppia
ERROR occured

Error Log
ERROR: /home/mani114/opensource/oppia-android/utility/src/main/java/org/oppia/android/util/math/BUILD.bazel:101:19: KotlinCompile //utility/src/main/java/org/oppia/android/util/math:comparator_extensions_kt { kt: 1, java: 0, srcjars: 0 } for armeabi-v7a failed: Worker process did not return a WorkResponse: ---8<---8<--- Start of log, file at /home/mani114/.cache/bazel/_bazel_mani114/448f11c285b7b190ad4fd87f081da82c/bazel-workers/worker-10-KotlinCompile.log ---8<---8<--- WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by io.bazel.kotlin.builder.toolchain.KotlinToolchain$JDepsInvoker (file:/home/mani114/.cache/bazel/_bazel_mani114/448f11c285b7b190ad4fd87f081da82c/external/io_bazel_rules_kotlin/src/main/kotlin/kotlin_worker.jar) to method com.sun.tools.jdeps.Main.run(java.lang.String[],java.io.PrintWriter) WARNING: Please consider reporting this to the maintainers of io.bazel.kotlin.builder.toolchain.KotlinToolchain$JDepsInvoker 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 ---8<---8<--- End of log ---8<---8<--- Target //:oppia failed to build Use --verbose_failures to see the command lines of failed build steps. INFO: Elapsed time: 122.003s, Critical Path: 60.89s INFO: 214 processes: 3 internal, 202 linux-sandbox, 9 worker. FAILED: Build did NOT complete successfullyApproaches already used to resolve the issue
No response
Additional information
No response
Beta Was this translation helpful? Give feedback.
All reactions