Why is JaCoCo 0.8.8 release so restrict on imports of org.objectweb.asm.* packages?

[Peter Kirschner]

Hi everybody,

is it really necessary to be so restrict on imports of                                         org.objectweb.asm.commons;version="[9.2.0,9.3)"
org.objectweb.asm.tree;version="[9.2.0,9.3)"
org.objectweb.asm;version="[9.2.0,9.3)"

Usually I would expect that JaCoCo is a consumer of the library and therefor it should suffice to restrict the range to version='[9.2,10)'
That would allow a more flexible usage. But I haven't checked the code actually.

Is it really necessary?

[Marc Hoffmann]

Hi Peter,

good question. I would assume ASM strictly sticks to semantic versioning so from API perspective this should be save.

On the other hand our extensive regression tests only run on the specific update version, there is a small risk that something breaks with the newer ASM version.

Evgeny, what do you think? Can we set the upper (exclusive) boundary to the next Major version?

Cheers,

-marc

--
You received this message because you are subscribed to the Google Groups "JaCoCo and EclEmma Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jacoco+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/4b4964e8-be64-47a4-9b76-035968688d1fn%40googlegroups.com.

[Marc Hoffmann]

Here is the official statement: https://asm.ow2.io/faq.html#Q15

To view this discussion on the web visit https://groups.google.com/d/msgid/jacoco/2FE6870E-A43F-467B-A97A-F61154DC709E%40mountainminds.com.