Hi Manuel. Rather than saying they "replace" anything, I'd prefer to say that they are a different approach to using JS libraries in the Jenkins UI and that you would use one or the other, but not both.
The older plugins that you linked to are for use in the "traditional" (bind to global scope) mode where in the case of jQuery, there can only be one version in play at a given time. The approach in js-libs is that they are all "detached" from the global scope (allowing multiple "concurrent" versions etc) + are usable in a CommonJS type modular JS system. If interested, there's more info on these topics on jenkins-js-modules <https://github.com/tfennelly/jenkins-js-modules> and jenkins-js-builder <https://github.com/tfennelly/jenkins-js-builder>. -- 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/6c9bf44c-5570-46d8-883d-21378ebaa524%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
