Replies: 3 comments 6 replies
-
I'm really sorry, no, it was a lot of work even to get it working with Java 1.7. Actually for the next major release I was considering making Java 1.8 the minimum requirement. However as long as you're building on a JDK with version at least 1.7 (even if you're targeting 1.6), for many applications you can do all the scanning at build-time, on the build machine, and just save the scan results somewhere that the 1.6 runtime can access them: https://github.com/classgraph/classgraph/wiki/Build-Time-Scanning |
Beta Was this translation helpful? Give feedback.
-
PS feel free to try to port the code to Java 1.6, if you're feeling ambitious! You could use the Animal Sniffer Maven plugin to find parts of the code that are incompatible with Java 1.6 (or just try changing the target version to 1.6, and fix the errors that come up -- although Animal Sniffer also catches semantic errors, not just syntax errors between versions). |
Beta Was this translation helpful? Give feedback.
-
But... why..... 1.8 is EOL already :( there are so many downsides to enabling backwards compatibility, or even just supporting it. Definitely make the min 1.8, actually could even go 11 at this point - Trying to keep jackson json version 1.8 compatible is becoming a nightmare for version 3..... -1 for this request, -100 even |
Beta Was this translation helpful? Give feedback.
-
Hi Guys:
I am intended to use this library with jdk1.6, is this possible ?
Regards,
Joshua
Beta Was this translation helpful? Give feedback.
All reactions