Add severity option for validators #131
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Background
Adds a property to set the severity of validators for the
validate
andbuild
tasks.The default severity for the build task remains
WARNING
while the default for thejarValidate
task is updated toERROR
. This prevents the double-printing of warning events during the build so that by default the jarValidate task only prints validation events that would have caused it to fail.Note: not all smithy-cli commands have a
severity
option.Testing
Executed a build with and without this change and confirmed the
After this change:
Links
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.