Closed lostiniceland closed 3 years ago
Hi @lostiniceland,
I will have today a look if can simply switch to the latest ASM version. If yes, I would prepare a release candidate for a new version of JQA.
jQA 1.10.0 should be able to read Java 17 classes (it comes with ASM 9.1 which according to https://asm.ow2.io/versions.html should support it).
@lostiniceland: Which jQA version and distribution (Maven or CLI) are you using?
1.9.1 which was referenced in the Getting-Started CLI section
Can you try with 1.10.0? The getting started page has been updated.
@DirkMahler The guide should mention, that there might be a more recent version of jQA.
@DirkMahler Maybe we should consider a 1.11.0 with support for JDK 18 by only updating the ASM version we use?
@DirkMahler I can confirm that 1.10.0 works with Java 16 (after fixing the cli shell with the solution mentioned here)
@obfischer It's updating the dependency as well as (possibly) increasing the ASM API version in the VisitorHelper of the Java plugin.
@lostiniceland I adopted the hint in the getting started page (sadly we cannot link directly to the latest distribution).
@DirkMahler We could use this link to Maven Central Repository Search: https://search.maven.org/artifact/com.buschmais.jqassistant/jqa-uber-parent
Closing, as 1.10.0 solves the issue
The next version will use ASM 9.2 and will be able to scan also Java 18 bytecode.
In preparation for the upcoming Java LTS 17, supporting the scanning of Java 16 would be nice.
At the moment the result is this