The Maven plugin should support the skip configuration parameter, as many others do (e.g. clean, help), like:
<configuration>
<skip>true</skip>
</configuration>This is useful when you want to skip the execution in specific builds, without requiring dedicated Maven profiles. The corresponding user property defined in the Mojo should have a scope like in jsonschema.skip to avoid clashes with other plugins, and should take precedence over the static plugin configuration above.
For instance, I'd like to generate schemas only when building a new release version of an artifact, not in regular CI jobs. With the above
configuration I'd be able to skip the generation and have faster CI jobs, while activating it in release jobs overriding it with -Djsonschema.skip=false.
The Maven plugin should support the
skipconfiguration parameter, as many others do (e.g. clean, help), like:This is useful when you want to skip the execution in specific builds, without requiring dedicated Maven profiles. The corresponding user property defined in the Mojo should have a scope like in
jsonschema.skipto avoid clashes with other plugins, and should take precedence over the static plugin configuration above.For instance, I'd like to generate schemas only when building a new release version of an artifact, not in regular CI jobs. With the above
configuration I'd be able to skip the generation and have faster CI jobs, while activating it in release jobs overriding it with
-Djsonschema.skip=false.