![]() ![]() This fails expectedly since mod.a no longer exports the package required. Then it compiles the variant version of mod.a in src3 and runs the main program again. The shell script run.sh compiles src1, then compiles src2, then runs the main program, which succeeds since it successfully depends on mod.a from src1. There are three subdirs: src1 contains mod.a that exports a package src2 contains mod.b that requires mod.a and that has a main-class src3 is a modification of mod.a that doesn't export the necessary package. The attached test case is a bit cumbersome but it's the smallest I could get. Instead, it's a misconfiguration of modules. This has nothing to do with JNI, and has nothing to do with the JDK installation. In a modular environment, if a dependent class cannot be found because of system misconfiguration, a spurious message can be emitted:Įrror: A JNI error has occurred, please check your installation and try againįollowed by an exception that gives the exact problem. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |