Currently I’m using a lot of inline JS packages to provide a rich UI for the warnings plugin. I want to use the same UI modules in another plugin so I am wondering what would be the best way to provide these features.
Should I create a new API plugin for each of these dependencies? E.g. I’m using in warnings plugin - bootstrap - jquery And a lot more. Should I create one new plugin for each of those dependencies? Then we have something like warnings-plugin +- bootstrap-api-plugin \- jquery-api-plugin and so forth… Or is this some kind of overkill? How do we handle conflicts with Jenkins core UI packages? In Jenkins core we currently bundle some very old libraries that do not play nicely with my packages above. Should core get also some detached plugins for the UI part? E.g. in core we currently have hard-coded bootstrap 3 that is not compatible with bootstrap 4. In order to use bootstrap 4 in my plugin I need to replace the layout jelly tag with an individual version that does not load those problematic modules. -- 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/9E8B5586-4524-4843-A7DE-D63D738A2F2F%40gmail.com. For more options, visit https://groups.google.com/d/optout.
