Scenario

This is currently the most recent version of jacoco available at Maven Central:

https://repo1.maven.org/maven2/org/jacoco/org.jacoco.core/0.8.10/org.jacoco.core-0.8.10.pom

Its OSGi bundle

https://repo1.maven.org/maven2/org/jacoco/org.jacoco.core/0.8.10/org.jacoco.core-0.8.10.jar

has quite restrictive version range dependencies on org.objectweb.asm:

org.objectweb.asm;version="[9.5.0,9.6)",org.objectweb.asm.commons;version="[9.5.0,9.6)",org.objectweb.asm.tree;version="[9.5.0,9.6)"

There is now a new ASM version 9.6 available:

https://repo1.maven.org/maven2/org/ow2/asm/asm/9.6/

It would be nice to have org.jacoco artifacts available at Maven central compatible with the latest ASM version.

I wonder in general if it's intentional to have such a restrictive range rather than [9,10) or '`9.5.0,10) for example. There's no doubt a good reason. I'm just curious.

Current Behaviour

Can't work with latest version of ASM.

Wanted Behaviour

Would like to work in combination with latest version of ASM.

Possible Workarounds

Use older version of ASM.