Declaring it as direct dependency will work but feels wrong from an architectural viewpoint. Isn‘t there anything we can do to make this process simpler for Jenkins plugins? Dependency resolution of Jenkins plugin versions is done dynamically when Jenkins starts so it does not make much sense that Maven checks the static build-time versions of plugins. These version will be never user in practice, normally you always run Jenkins with the latest versions.
> Am 18.08.2018 um 14:40 schrieb Daniel Beck <[email protected]>: > > > >> On 17. Aug 2018, at 23:55, Aldrin Leal <[email protected]> wrote: >> >> What should be the right approach? > > If you cannot update your dependencies to make the transitive dependencies > consistent, try adding explicit dependencies on: > > +-org.jenkins-ci.plugins:junit:1.3 > +-org.jenkins-ci:annotation-indexer:1.12 > > -- > 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/99A4CC71-3B23-44DD-ADA7-468D41F7F7FA%40beckweb.net. > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5C0F6D1E-39B2-413E-BFD5-B91C67B62FD1%40gmail.com. For more options, visit https://groups.google.com/d/optout.
