On Tue, Feb 10, 2015 at 9:19 AM, Vaclav Tunka <[email protected]> wrote: > what about considering JBoss Modules? > > TL;DR; Modular classloading instead of hierarchical.
Jenkins *does* use modular class loading at the plugin level; for historical reasons this is not applied to libraries shipped in core. If we were starting from scratch, certainly JBoss Modules, OSGi (at least the module layer), etc. etc. would be the only sane way to manage a thousand plugins. (By way of background, I worked for years on the NetBeans module system, which has roughly similar capabilities.) But the question is how such a change could be retrofitted into the complex existing system in Jenkins without major compatibility problems. -- 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/CANfRfr025nvYwBk6oe51O3S5McJAMYk5m7_nPWZX5LfyuOG15w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
