On Sat, Aug 18, 2018 at 2:16 PM Ulli Hafner <[email protected]> wrote: > Declaring it as direct dependency will work but feels wrong
I would rather suggest using `<dependencyManagement>`. > Isn‘t there anything we can do to make this process simpler for Jenkins > plugins? > […] > These version will be never user in practice, normally you always run Jenkins > with the latest versions. That is why I advocate JENKINS-47498¹ to address this and other issues. You would merely pick some number for the parent POM (or perhaps some other property or meta-import in your POM), giving you a set of dependency management guaranteed to be consistent; and if you wanted to use some newer APIs, just pick a newer (probably the newest) number. ¹ https://issues.jenkins-ci.org/browse/JENKINS-47498 -- 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/CANfRfr0XO456Ec6kAOQVBNYWv1VmEOqRHxFdhPs2M-L2xA4_0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
