On Fri, May 1, 2020 at 11:34 PM Richard Bywater <[email protected]> wrote: > I've got the build to work again by removing recommendedConfigurations and > switching to explicitly building the minimum version of Jenkins that is > referenced in the pom.xml
This makes no sense. If you _only_ want to build the version referenced in `pom.xml`, just buildPlugin() The point of `configurations` is to build against _newer_ versions as well. > I also could fix the issue with upping the slf4jversion parameter but it > seemed wrong to do this when I don't have any particular reason in the plugin > to have that particular version. I guess I kind of expected the bom to handle > that type of thing for me It does. You should switch to a 4.x version of the parent POM. > the earliest LTS version which has greater than x% usage We only ship security patches to the current LTS, so anything older is technically unsupported. I remain opposed to having an implicit Jenkins version in `recommendedConfigurations` and in general to the notion of having plugin `Jenkinsfile`s import an unversioned tip of `pipeline-library`. -- 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/CANfRfr2Laouye2t-hkMO85BxzOpHjmuZb23Q00SJwAuu6PNRtw%40mail.gmail.com.
