On Fri, Oct 9, 2015 at 4:25 PM, Arnaud Héritier <[email protected]> wrote: > you are proposing to rewrite the dependencies resolution mechanism of maven > and friends in bash ?
Of course not! First of all I said nothing about Bash. Second, Jenkins dependency semantics are pretty simple: plugins identified by a single `shortName`, minimum versions using a fairly limited version parser, optional flag. Nowhere near as complex as Maven dependencies. > How will you resolve conflicts/constraints betweens dependencies ? There are no conflicts or constraints. You pick the newest version requested from any dependency, or even just pick the version offered on the update center (ideally signaling an error if that is not new enough for some dependency, which of course should not happen unless someone else screwed up). > we have nowadays no solution to propose such service if jenkins server isn’t > started. Why? Parsing out dependencies from plugin JAR manifests is a pretty short Perl script or whatever. Or you could reuse Jenkins classes in batch mode if you were writing the tool in Java; `plugin-compat-tester` does that, for example. > This library will never be able to have a 2.0 version with backward > incompatible changes without breaking several dozen or hundred of plugins Sure; that is true of any incompatible change in a widely used API, which is why we strive hard to retain backward compatibility. What is your point? Marking the dependency optional would make no difference. Either you are using the WF step and you are affected, or you are not using it and you are not affected. > a dedicated workflow library/plugin hosting all the integrations Unmaintainable and antimodular. We do not expect one plugin to host all known `Builder` implementations so I do not see why `Step` should be any different. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr209AucVnBfcDyW2BjPjP9N-y_M-m_k3%2BBBV4vXbhTQ_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
