JMS Messaging

Dependencies

Required

commons-lang3 v3.x Jenkins API ≥ 3.18.0-98.v3a_674c06072d

commons-text API ≥ 1.13.1-176.v74d88f22034b_

JSON Path API ≥ 2.9.0-148.v22a_7ffe323ce

Pipeline: API ≥ 1373.v7b_813f10efa_b_

Pipeline: Groovy ≥ 4165.vf547819734da_

Pipeline: Job ≥ 1540.v295eccc9778f

Apache HttpComponents Client 4.x API ≥ 4.5.14-269.vfa_2321039a_83

Folders ≥ 6.1026.ve06dfa_cf31c3

Credentials ≥ 1415.v831096eb_5534

Docker Commons ≥ 457.v0f62a_94f11a_3

Jackson 2 API ≥ 2.18.3-402.v74c4eb_f122b_2

jsoup API ≥ 1.21.1-52.v96e4041b_60fd

Mailer ≥ 489.vd4b_25144138f

Matrix Project ≥ 849.v0cd64ed7e531

Script Security ≥ 1373.vb_b_4a_a_c26fa_00

Optional

Pipeline: Step API ≥ 704.ve4f0967e98fa_

Dependent plugins

Declaring a dependency

As a plugin developer you can use this plugin as dependency of your plugin by adding a dependency tag to your POM.

To add the latest version of this plugin as a maven dependency, use the following:

<dependency>
    <groupId>org.jenkins-ci.plugins</groupId>
    <artifactId>jms-messaging</artifactId>
    <version>2.0.0</version>
</dependency>

No dependent plugins found