The name of this file set property.
The paths that make up this file set. Can either be files or directories.
Relative paths are resolved against the project base dir.
The name of this file set property.
The paths that make up this file set. Can either be files or directories. Relative paths are resolved
against the project base dir.
A list of ANT-style include patterns that will be used to filter the contents of the input paths.
The name of the property that provides include patterns for this file set.
The extension will automatically get the value of this property.
A list of ANT-style exclude patterns that will be used to filter the contents of the input paths.
The name of the property that provides exclude patterns for this file set.
The extension will automatically get the value of this property.
The normalization strategy, defaults to RELATIVE_PATH.
For a full list of strategies, please refer to the extension user manual.
Additional input file set properties.
Additional scalar input properties.
Properties which should be ignored for the purposes of caching.
The name of this file property.
The path of the file. Relative paths are resolved against the project base dir.
Allows you to activate caching for goals that the extension does not support out of the box.
The given reason should document why you decided that caching this particular goal was safe.
Use with caution and be sure to declare all inputs and outputs of the goal before activating this.
Not all goals are worth caching. If something is IO-bound (e.g. copying/creating zips), caching will only
make it slower.
The reason why the outputs of an execution can't be cached.
E.g. "it accesses undeclared input files"
The supplied reason should fit well in the following sentence:
"Build caching was not enabled for this goal execution because 'reason'."
Additional output file properties.
Additional output directory properties.
Configures inputs for this execution.
All inputs are combined into the cache key that is used to look up existing outputs.
Configures outputs for this execution.
All outputs are packed into the cache archive and unpacked again on a cache hit.
Outputs can also be marked as non-cacheable, e.g. when you know that the goal execution
has some hidden inputs that you can't model, like network requests to other systems.
Configures local state for this execution.
Local state files are neither inputs, nor outputs. A typical example would be temporary directories.
They are deleted when the outputs of a goal execution are loaded from the cache.
Configures nested properties for this execution.
Use this whenever a goal has a complex input object that you can't add as a scalar input property.
Configures iterated properties for this execution.
Use this whenever a goal has a list of complex input objects that you can't add as a scalar input property.
The groupId of the target plugin.
May be omitted, in which case the default plugin groups will be considered
Execution-specific configuration
Configures inputs that are common to every execution of this plugin.
All inputs are combined into the cache key that is used to look up existing outputs.
Configures outputs that are common to every execution of this plugin.
All outputs are packed into the cache archive and unpacked again on a cache hit.
Outputs can also be marked as non-cacheable, e.g. when you know that the goal execution
has some hidden inputs that you can't model, like network requests to other systems.
Configures local state that is common to every execution of this plugin.
Local state files are neither inputs, nor outputs. A typical example would be temporary directories.
They are deleted when the outputs of a goal execution are loaded from the cache.
Configures nested properties that are common to every execution of this plugin.
Use this whenever a goal has a complex input object that you can't add as a scalar input property.
Configures iterated properties that are common to every execution of this plugin.
Use this whenever a goal has a list of complex input objects that you can't add as a scalar input property.
Tags that will be added to the custom value section of your build scans.
Links that will be added to the custom value section of your build scans.
Name-value pairs that will be added to the custom value section of your build scans.
A list of ANT-style patterns to ignore. The patterns are matched against the relative path
of a resource, e.g. 'META-INF/LICENSE.*'
The normalization configuration for runtime class paths. A typical example of a runtime
class path is the test class path of the surefire plugin.
Allows you to add project-specific tags, links and values to your build scans
Allows you to control which inputs are considered relevant when creating cache keys
Allows you to control the cacheability of the plugins in this project