On Thu, May 25, 2023 at 5:24 AM Ullrich Hafner <ullrich.haf...@gmail.com> wrote: > Rather than reinventing the wheel we should use more of those rock-solid > component [sic] that are already on the market.
Indeed, and I suspect this was the fatal flaw behind Tom Fennelly's effort several years back: his homegrown dynamic linker never reached critical adoption. In contrast, Webpack module federation is a general component that is already on the market and widely deployed. > it does not make sense to create our own version of ECharts, or Bootstrap, etc It _does_ make sense to package third-party libraries (either Java or JavaScript) as Jenkins library plugins in order to facilitate dynamic linking. This is a consequence of the fact that we maintain a homegrown plugin distribution, installation, and loading system (and it is far too late to distribute, install, and load Jenkins plugins through some generalized method). -- 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/CAFwNDjqRuWnhC9XecYF%2Bpo80rrz3q5fYg_X6QR%2BEwmwP4kJRjg%40mail.gmail.com.
