Not only ASM for Java 9 is coming, one of contributors is JDK committer, and the current ASM state is that there is still no final specs for some attributes for Java 9 and therefore ASM can't even release any beta yet because it will be broken soon anyway.
Gesendet: Donnerstag, 16. März 2017 um 13:46 Uhr Von: "Thomas Watson" <tjwatson@xxxxxxxxxx> An: cross-project-issues-dev@xxxxxxxxxxx Betreff: Re: [cross-project-issues-dev] ASM for Java 9 (was Re: Java 9 Readiness)
ASM 6 is in a branch for Java 9 support . So I think it is coming.
----- Original message -----
From: Ed Willink <ed@xxxxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject: [cross-project-issues-dev] ASM for Java 9 (was Re: Java 9 Readiness)
Date: Thu, Mar 16, 2017 7:16 AM
I kind of feel that the ASM guys know that Java 9 needs support. One day it will be there, might already be on a branch just like JDT's BETA. An Orbit update will no doubt follow.
For Oxygen/Update 1 usage in Eclipse each project has to do its best. My projects offer at least one old Eclipse version of compatibility, so I cannot mandate a brand new Java 9 ASM for Mars users.
Fortunately JaCoCo have identifed that ASM works fine just so long as you pretend that Java 9 class files are Java 8.
Since I use ASM for @NonNull analysis only, I can have a very simple read-time workaround:
* Set true if ASM has Java 9 support, else false and Java 9 classes will be downgraded to look like Java 8.
private boolean hasOpcodes_V1_9 = false;