The directory containing generated classes.

The path to the context.xml file to use.

The comma separated list of tokens to exclude when doing a way overlay.

The comma separated list of tokens to include when doing a war overlay.

Controls the safety check that prevents a snapshotPluginVersionOverride from switching to a different release version.

No description.

Optional string that represents "groupId:artifactId" of Jenkins core jar. If left unspecified, the default groupId/artifactId pair for Jenkins is looked for.

Optional string that represents the version of Jenkins core to report plugins as requiring. This parameter is only used when unbundling functionality from Jenkins core and the version specified will be ignored if older than the autodetected version.

[ws|tab|CR|LF]+ separated list of package prefixes that your plugin doesn't want to see from the core.

Tokens in this list is prefix-matched against the fully-qualified class name, so add "." to the end of each package name, like "com.foo. com.bar."

The directory for the generated WAR.

List of dependency version overrides in the form groupId:artifactId:version to apply during testing. Must correspond to dependencies already present in the project model or their transitive dependencies.

Path to a Jenkins WAR file with bundled plugins to apply during testing.

Dependencies already present in the project model or their transitive dependencies will be updated to the versions in the WAR.

May be combined with overrideVersions so long as the results do not conflict.

The version of the WAR must be identical to jenkins.version.

Change the classloader preference such that classes locally bundled in this plugin will take precedence over those that are defined by the dependency plugins.

This is useful if the plugins that you want to depend on exposes conflicting versions of the libraries you are using, but enabling this switch makes your code susceptible to classloader constraint violations.

Name of the plugin that Jenkins uses for display purpose. It should be one line text.

Additional information that accompanies the version number of the plugin. Useful to distinguish snapshot builds. For example, if you are building snapshot plugins from Jenkins, you can put the build number in here by running Maven with "-Dplugin.version.description=$BUILD_TAG"

Optional - the version to use in place of the project version in the event that the project version is a -SNAPSHOT. If specified, the value must start with the project version after removing the terminal -SNAPSHOT, for example if the project version is 1.2.3-SNAPSHOT then the snapshotPluginVersionOverride could be 1.2.3-rc45.cafebabe-SNAPSHOT or 1.2.3-20180430.123233-56, etc, but it could not be 1.2.4 as that does not start with the project version. When testing plugin builds on a locally hosted update centre, in order to be allowed to update the plugin, the update centre must report the plugin version as greater than the currently installed plugin version. If you are using a Continuous Delivery model for your plugin (i.e. where the master branch stays on a version like 1.x-SNAPSHOT and releases are tagged but not merged back to master (in order to prevent merge conflicts) then you will find that you cannot update the plugin when building locally as 1.x-SNAPSHOT is never less than 1.x-SNAPSHOT. Thus in order to test plugin upgrade (in say an acceptance test), you need to override the plugin version for non-releases. Typically you would use something like git-timestamp-maven-plugin to populate a property with the version and then use this configuration to provide the version.
See also: failOnVersionOverrideToDifferentRelease

List of exclusions to upper bound updates in the form groupId:artifactId. Must not be provided when useUpperBounds is false.

Whether to update all transitive dependencies to the upper bounds. Effectively causes the same behavior as the requireUpperBoundDeps Enforcer rule would, if the specified dependencies were to be written to the POM. Intended for use in conjunction with overrideVersions or overrideWar.

Single directory for extra files to include in the WAR.

The comma separated list of tokens to exclude from the WAR.

The comma separated list of tokens to include in the WAR.

The list of webResources we want to transfer.

The directory where the webapp is built.

Directory to unpack dependent WARs into if needed