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'."
The groupId of the target plugin.
May be omitted, in which case the default plugin groups will be considered
The outputs of this plugin.
Changes here will affect every execution of the plugin.
Consider using the <executions> configuration for more fine-grained control
Execution-specific configuration
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