On Wed, Nov 29, 2017 at 6:47 AM, Victor Martinez <victormartinezru...@gmail.com> wrote: > 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.
+1, makes sense. `maven-release-plugin` _can_ be run in subdirectories but that is really not the conventional usage. > I know it might be a bit of > overwhelming work (git repos, move history, Jenkins pipelines...) Probably not that hard. I would not bother moving history (i.e., `git filter-branch` black magic) in this case, since there are only 126 commits, and the history is not all that interesting—it is not likely someone three years from now is going to want to `git bisect` why some version number was incremented in a `package.json`. > no > idea how to proceed (maybe raising a jira ticket in case we agree) Probably just requires the usual `HOSTING` ticket if there is consensus. Do you expect to help maintain this stuff? Adding Tom Fennelly to CC. -- 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/CANfRfr39S6foTNMjbatbvijTjMYd-teyo9ft%3DNQXd66ypw_ULQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
