We should also take a step back and see if these problematic deps really need to exist at all. Most uses of ASM should be deleted if at all possible. I was able to remove Digester and thus, I guess, ASM from the Subversion plugin without much difficulty. I do not understand Token Macro well enough to understand whether it fundamentally needs ASM there (nor do I intend to spend time on that plugin given that Pipeline rendered it obsolete). The Stapler dep on ASM turned out to be just an overengineered way of solving a problem which can be addressed by adding a single flag to javac (though we need to update the parent POMs of plugins to avoid needing ASM at runtime for them).
JNR may be a similar story. I see all of two usages in core—both disabled unless you set a system property. Just deleting it all may be easier than having subtle debates about class loader behavior and compatibility policy. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3NPD3b%2BQ2TiQGLyqicuA2-gEby-%2BCJgLGtViXOw1Uh_w%40mail.gmail.com.
