Shigeru Chiba
Shigeru Chiba
The modified bytecode needs (at most) the `javassist.runtime` package only.
So far no. Isn't it acceptable to make a separate jar by yourself? Do you need an official repo on maven?
OK, but I'm still quite a novice in maven repo. Do I need to write a separate pom.xml for that runtime repo?
Thanks. Give me time to do this.
The code dependent on `java.rmi` will be removed. `java.rmi` in `src/test/test2/Inner.java` has been already removed. I could not see `java.rmi` in `JvstTest3.java`, `StackMapTest.java`, or `BytecodeTest.java`. What am I missing?
OK, I'll check them. By the way, I removed `java.rmi` from `Inner.java` today. So it's not your fault that you didn't notice that.
This problem is caused by the same reason as mentioned here, http://www.javassist.org/html/javassist/CtClass.html#toClass() We must find a similar work-around to bypass the strict access control by jdk 17.
Giving this option to the JVM `--add-opens java.base/java.lang=ALL-UNNAMED` is a quick workaround.
@takezaki , I have just released 3.29.0-GA.
@AlanBateman, I've worked on this. Now the API supports MethodHandles.Lookup. The version of Javassist including this work will be released soon. I could fix the problem without changing the original...