Bug#923284: Seemingly miscompiles with jdk-11

[Sjoerd Simons]

On Tue, 2019-02-26 at 11:35 +0100, Emmanuel Bourg wrote:
> Le 26/02/2019 à 10:20, Sjoerd Simons a écrit :
> 
> > I've atteched the output of running docker build on the DockerFile
> > i
> > attached to reproduce the issue; The relevant part in the gradle
> > build
> > seems to be:
> 
> Thank you! The "Malformed jar" message is just a warning. The actual
> issue is:
> 
> > Caused by: java.lang.UnsupportedOperationException: This feature
> > requires ASM7
> > 	at
> > org.objectweb.asm.ClassVisitor.visitNestHost(ClassVisitor.java:150)
> > 	at org.objectweb.asm.ClassReader.accept(ClassReader.java:541)
> > 	at org.objectweb.asm.ClassReader.accept(ClassReader.java:391)
> > 	at
> > org.gradle.api.internal.tasks.compile.incremental.asm.ClassDependen
> > ciesVisitor.analyze(ClassDependenciesVisitor.java:75)
> 
> Most likely triggered because the recompiled bsh uses Java 11
> bytecode.
> This can be fixed either by targeting a pre Java 11 release in the
> bsh
> build, or by patching Gradle to use Opcodes.ASM7.

ASM7 mode seems to have been introduced in the gradle v5.x series. Not
sure if it makes sense for buster to upgrade to that (I really don't
know much about java, so no idea about the impact)? 

That said making all gradle dependencies target pre-Java 11  probably
doens't scale either?

-- 
Sjoerd Simons <sjoerd at debian.org>