On Sunday, February 18, 2024 at 1:42:00 PM UTC-7 Michael wrote:
Hi Solved this way + <dependency> + <groupId>org.jenkins-ci.plugins</groupId> + <artifactId>junit</artifactId> + <version>1119.1121.vc43d0fc45561</version> + <scope>test</scope> + </dependency> + <dependency> + <groupId>org.jenkins-ci.plugins</groupId> + <artifactId>script-security</artifactId> + <version>1175.v4b_d517d6db_f0</version> + <scope>test</scope> + </dependency> Is this the correct way? That is a valid way to solve it, though most plugin maintainers prefer to let the plugin bill of materials manage the versions of dependencies when they are available from the plugin bill of materials. The "Improve a plugin" tutorial <https://www.jenkins.io/doc/developer/tutorial-improve/> includes a section on using the plugin bill of materials <https://www.jenkins.io/doc/developer/tutorial-improve/use-plugin-bill-of-materials/> . It also has a section on updating the minimum Jenkins version <https://www.jenkins.io/doc/developer/tutorial-improve/update-base-jenkins-version/> (you probably want 2.414.3 rather than 2.410). It also has a section on updating the parent pom <https://www.jenkins.io/doc/developer/tutorial-improve/update-parent-pom/> that will allow you to run tests with Java 21 and Java 17 <https://www.jenkins.io/doc/developer/tutorial-improve/add-a-jenkinsfile/> so that you're confident the plugin works on all the JDKs that Jenkins supports. Thanks very much for adopting the plugin! 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/ca8c242d-1f6d-4ba8-aad6-fe28a29ed6b0n%40googlegroups.com.
