Passing -Djenkins.version=2.164.1 is the technique that many of the plugins now use to test Java 8 and Java 11 compilation and test. Can you further describe how it fails when you use that argument to maven? It may be a failure that is familiar to those working on Java 11.
On Tue, Apr 23, 2019 at 4:47 AM Ullrich Hafner <[email protected]> wrote: > Is it possible, to specify a different minimum Jenkins version in a plugin > for the runtime and the tests? > > Currently my plugin is compatible with Jenkins 2.89.1 (from an API point > of view). > > However, due to some dependencies in my integration tests (declarative > pipeline, etc.) the tests that use Jenkins test harness and the injected > tests fail since they want a dependency to a Jenkins version >= 2.150.1. > I tried to use -Djenkins.version=2.150.1 when starting the test but this > seems not to work. > > > > -- > 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/610AEA80-3D9F-454C-B363-BBA35FA66DDB%40gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- 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/CAO49JtHLkeCaSbSR_g5kzWsWPMTa7L0ZemRCH8JbT%2BT9yavLiw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
