--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/abd68b18-c265-4dca-a5a2-0255c16dfda3n%40googlegroups.com.
--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/NhV_o6zxbzw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/9c2d0cbb-2972-4e88-a51b-c53a5f39f5e4n%40googlegroups.com.
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr3NPD3b%2BQ2TiQGLyqicuA2-gEby-%2BCJgLGtViXOw1Uh_w%40mail.gmail.com.
We do NOT guarantee that system properties will remain unchanged and functional indefinitely. These switches are often experimental in nature, and subject to change without notice. If you find these useful, please file a ticket to promote it to an official feature
So breaking it is not the worst.
ASM is a dependency of the parser used (parboiled).
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1acCBAzdOGx_NzQHx3VpP62pd%3Dp%2BuuEK0Ajxo5_kpdtQ%40mail.gmail.com.
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpBuUqLfb7McWCZ6Ue2eMCGDj2vff9atO0_94VLykXCeQ%40mail.gmail.com.
the only remaining consumers of ASM in core will be Stapler and access-modifier
So should I look into the shading approach further?
accomplish the shading by making a dedicated module for the shaded JAR, but I didn't quite follow the concept
Recent weeklies no longer consume ASM. So shall we detach it to a
library plugin?
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjr6H53AJNa9YedKtSUOwNg4B7EayJshWZWW7TC3gucXfw%40mail.gmail.com.
Recent weeklies no longer consume ASM. So shall we detach it to a
library plugin?