-
Notifications
You must be signed in to change notification settings - Fork 51
[POC-Issue#5735]: support legacy automate excludeFromFailureFile
#202
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
Conversation
apply remove this
| private void logExcludeFromFailureFileSuppressions() { | ||
| log.info("logExcludeFromFailureFileSuppressions"); | ||
| log.info(violations.stream() | ||
| .map(violation -> String.format("%s:%s", violation.getViolationClass(), violation.getRule())) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| .map(violation -> String.format("%s:%s", violation.getViolationClass(), violation.getRule())) | |
| .map(violation -> String.format("%s=%s", violation.getViolationClass(), violation.getRule())) |
collision: (only works for one)
org.apache.maven.building.DefaultProblem=MissingOverride
org.apache.maven.model.merge.MavenModelMerger=ForLoopVariableCount
org.apache.maven.model.merge.MavenModelMerger=OneDeclarationPerLine
merge:
org.apache.maven.building.DefaultProblem=MissingOverride
org.apache.maven.model.merge.MavenModelMerger=ForLoopVariableCount,OneDeclarationPerLine
|
is this any good @oowekyala @adangel? A simple log to support manual c&p would give quick fix, without breaking anything as just logging. Then writing the keys into file could be next step, but not needed anymore. This is unique action, need to be done only once. So automation would be questionable. |
legacy automating excludeFromFailureFilelegacy automating excludeFromFailureFile
legacy automating excludeFromFailureFilelegacy automate excludeFromFailureFile
legacyprojects, auto-generation ofexcludeFromFailureFilepmd/pmd#5735maven-pmd-plugin: reactivatePMD- Best practices maven#2331mvn pmd:check > pmd.txtworkaround: