Rafael Winterhalter

As I understand it: The JDK might support older class files at some point?

I agree, generally speaking I would like to offer Byte Buddy as 1.8 class files. But I would want to allow adding a classifier or some other dependency configuration option,...

I made an attempt now with *byte-buddy-agent* and *byte-buddy-dep*. I compile the sources twice and create additional jars with the classifier *java8*. Would that work? Could you build Byte Buddy...

On a side note: ASM will always be compiled to Java 5. Will that be a problem?

Possibly, I can merge this in as a MR jar. This would blow up the artifact size, but I wonder if this really matters in today's world. Would make it...

Try the *mr-java8* branch. The JAR is 8 MB now, that is somewhat a concern, but I would not think that is an actual problem but rather a cosmetic one.

I think I will implement this then. Normally jar size is not important as dependencies are cached. For agents, the mr feature can be unrolled as one can strip one...

Just FYI: I worked out a small Maven plugin that takes the shaded ASM dependency, computes stack map frames and stores a Java 8 version of ASM in the multi-release...

Still edging out some things, but this will not take too long to figure out.

@sdeleuze Could you give this another try and: Build https://github.com/raphw/bytecode-update-maven-plugin Then build this branch: https://github.com/raphw/byte-buddy/tree/asm-multi-release After that, CDS should work with *byte-buddy.jar* without any warnings.