Matt
Vastly improved the output of generated `@interface` annotation classes. Was previously having problems with compilers not recognizing the types, but with e8b38c347044367318d40e9a9cb29e1d702380a2 that seems to be fixed 👍
Generally speaking per-VM test cases are the way to go to ensure there isn't any cross contamination of values across test invocations. And here there's only one test class with...
Could also use JPhantom like I have to generate missing classes.
Seems partially associated with #76 but with additional android / apk support
If you want to support recompile-decompile there are _other tools_ that support that. Grax is right on the scope issue. Adding a compiler can be a pain on multiple levels....
That wouldnt work, the classes/natives for attach dont exist in the JRE classpath *([related](https://github.com/GraxCode/JByteMod-Beta/issues/24#issuecomment-36))* But since you asked: ``` JByteMod-Beta-master\target>"C:\Program Files\Java\jre1.8.0_131\bin\java" -jar JByteMod-1.8.0.jar java.lang.UnsatisfiedLinkError: no attach in java.library.path at java.lang.ClassLoader.loadLibrary(Unknown...
Win 8.1 x64, java version is in the logs.
No because the attach process can't start.
Ok, that's a fine reason. An alternative if you'd wish to reduce compile time is compile these modified libraries to jar's and use them as local-repository dependencies. http://mark.koli.ch/maven-add-local-jar-dependency-to-classpath