Once JNR is removed from core in jenkinsci/jenkins#5979 (which is blocked on the merge, release, and widespread adoption of jenkinsci/pam-auth-plugin#20), then the only remaining consumers of ASM in core will be Stapler [1] and access-modifier [2]. It would be nice to eliminate these dependencies from core, which would allow us to detach ASM to an API plugin. I think we all agree that keeping ASM in core is a maintenance burden.
I suppose we could shade ASM into Stapler and access-modifier, but the last time I tried to do this for Guava I ran into weird Maven issues (MNG-5899?) and have not yet figured out a way to work around them. If anyone can think of a more clever way to eliminate our dependency on ASM, I would love to hear it. [1] https://github.com/jenkinsci/stapler/blob/980e6ca1a29aa31cee1356e2a4e22ac5274a86fa/core/src/main/java/org/kohsuke/stapler/ClassDescriptor.java#L320-L407 [2] https://github.com/jenkinsci/lib-access-modifier/blob/b68c0122e7cfc4772fb2f8ab485b2157fdfa53f8/access-modifier-annotation/src/main/java/org/kohsuke/accmod/restrictions/ProtectedExternally.java#L64-L78 -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjon-EtKcEKLGOp4Q5eqETm8WF3D8AN7EuQdqmP5jc%3DD0Q%40mail.gmail.com.
