On Fri, Oct 23, 2020 at 7:30 AM Radek Antoniuk <[email protected]> wrote: > how can I customise the list of plugins that the test runs with
Normally you do not do anything besides have plugins of interest in your Maven test classpath. `@WithPlugin` is tricky and rarely needed. > to detect a missing dependency in tests? What specifically are you trying to accomplish? Reproducing JENKINS-64002 in a test? Not going to work (see JENKINS-41827). Your mistake can be seen from `mvn dependency:tree`: [INFO] +- org.jenkins-ci.plugins:p4:jar:1.3.8:compile (optional) [INFO] | +- org.jenkins-ci.plugins:credentials:jar:2.3.13:compile (optional) You explicitly use the `credentials` plugin’s APIs, so you should have a direct dependency on it. (check `mvn dependency:analyze`) In general, use `optional` dependencies only with extreme care; see JENKINS-19508 for discussion. BTW your plugin does not build in `master`, perhaps because #277 introduced a mistake that #290 caught, or similar. -- 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/CANfRfr3RJHMRMN37iVJ_kW6f%2BmetF56H1_0GJdzx4FRhmKy4kw%40mail.gmail.com.
