Since the dependency is only required to make the test framework happy, I thought it is worth to see why it is not working as expected (since it works in maven I assumed that it is just a quick fix).
But you are right, for me as developer it is easier to increase the jenkins version (as this is already required by a different PR which increased the version due to an actual required new feature and not a test dependency). This also would help to enforce users to regularly upgrade their Jenkins instance. > Am 03.05.2019 um 14:38 schrieb Jesse Glick <[email protected]>: > > Is this time well spent, compared to just saying that anyone who wants > _new features_ from your plugin had also better be running a recent > LTS of core (or newer weekly)—not even necessarily the line with the > current security patches? Also see the discussion here: > > https://github.com/jenkinsci/plugin-pom/pull/167 > > If and when you have some critical, small, safe fixes that you would > want to backport even for users of obsolete core lines, this is not at > all difficult: > > https://gist.github.com/jglick/86a30894446ed38f918050c1180483e2 > > -- > 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/CANfRfr3c_C%3D18GPiZUzwAmCfyc4Xs7vTRMARLO-5G6rYHK6t7Q%40mail.gmail.com. > 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/627A4F90-0A27-4364-AEA1-08DB38DEA42D%40gmail.com. For more options, visit https://groups.google.com/d/optout.
