Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow to configure the plugin to fail on any severity #478

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

david-m-s
Copy link

This is necessary to ease the integration to cicd with requirements to not pass if any static code violation is found, without needing to configure the checkstyle, pmd and findbugs in depth to produce only error level. It s hard to configure each individual plugin (if at all possible) and can be difficult to maintain regarding future versions.

@david-m-s david-m-s requested a review from a team as a code owner January 15, 2025 12:15
@david-m-s david-m-s force-pushed the allow-to-fail-on-different-severities branch from a3fd025 to 6229b3d Compare January 17, 2025 08:02
…ues. This is necessary to ease the integration to cicd with requirements to not pass if any static code violation is found, without needing to configure the checkstyle, pmd and findbugs in depth to produce only error level, which is hard to do and can be difficult to maintain regarding future versions.

Signed-off-by: David Mas <david.mas@ocado.com>
@david-m-s david-m-s force-pushed the allow-to-fail-on-different-severities branch from 6229b3d to c7fc89a Compare January 17, 2025 08:07
@wborn wborn linked an issue Jan 19, 2025 that may be closed by this pull request
Comment on lines +374 to +375
throw new MojoFailureException(String.format("%n" + "Code Analysis Tool has found %d error(s)! %n"
+ "Please fix the errors and rerun the build. %n", errorCount));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This message may need an update as well depending on the configuration. Users might think only fixing errors should be enough but if you configure it to fail on warnings/info this is no longer the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add possibility to fail the build on any severity issues
2 participants