https://github.com/jenkinsci/git-plugin/commit/47b8042d969971d9d2d9eb1fc7c0082d4cac42ca should explain why... or at least that is the commit that introduced the dependency and the commit message looks reasonable...
(hint get to know what `git blame` does) On 27 October 2014 22:07, Kelly Brownsberger <[email protected]> wrote: > multi-scms is filling an important void in our world. It took a while to > get it working the way we wanted, but have been using it for some time now > with success. We're looking to move to Git from Subversion and in the > process we've discovered that the git plugin has a direct dependency on > multi-scm. This seems really strange. Why is this dependency here? It's > preventing us from referencing git from our fork of mulit-scms as it > creates a dependency cycle. > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
