Hi there, I've seen when using maven multimodes git repos in Jenkins plugins are mostly based on the same general versioning, such as the previous pipeline-plugin <https://github.com/jenkinsci/pipeline-plugin>, blueocean <https://github.com/jenkinsci/blueocean-plugin>, but I've found a minor discrepancy in that particular assumption and it's about the js-libs <https://github.com/jenkinsci/js-libs>.
This particular repo combine different plugins and each plugin is a maven module with a different version, for instance: - ace-editor <https://github.com/jenkinsci/js-libs/tree/master/ace-editor> got 1.2.2 version - bootstrap <https://github.com/jenkinsci/js-libs/tree/master/bootstrap> got 1.3.3 version - numeraljs <https://github.com/jenkinsci/js-libs/tree/master/numeraljs> got 1.1.1 version - ... I'd like to purpose to standardise as individual git repos therefore their release lifecycle and versioning can be independent and also get the benefits of using different parent POM versions. I know it might be a bit of overwhelming work (git repos, move history, Jenkins pipelines...), and no idea how to proceed (maybe raising a jira ticket in case we agree) but IMO it's worth to keep some homogenous standard. What do you think? Cheers -- 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/82ccb4a1-ef4f-4e9d-8fd0-63984c6a6264%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
