[core] Force disable suppressions (PMD + CPD)

[kloessst]

Description:
Hello,

PMD itself has the option -showsuppressed, to disable suppressions added to the code (via SupressWarnings or comment filtering). Does something similar exist for CPD? I would appreciate such a feature and would gladly contribute, if it doesn't exist yet.

Edit:
It seems like PMD uses this option to create another section in the report:

// suppressed violations
            if (showSuppressedViolations) {
                for (Report.SuppressedViolation s : suppressed) {
                    writeNewLine();
                    xmlWriter.writeStartElement("suppressedviolation");
                    xmlWriter.writeAttribute("filename", determineFileName(s.getRuleViolation().getFilename()));
                    xmlWriter.writeAttribute("suppressiontype", s.suppressedByNOPMD() ? "nopmd" : "annotation");
                    xmlWriter.writeAttribute("msg", s.getRuleViolation().getDescription());
                    xmlWriter.writeAttribute("usermsg", s.getUserMessage() == null ? "" : s.getUserMessage());
                    xmlWriter.writeEndElement();
                }
            }

Is it be possible to add an option which disables all suppressions completely?

Best regards,
Stefan

[adangel]

Right -showsuppressed shows all the violations, that are suppressed, which is almost what you want - but for PMD only.

You want to run PMD/CPD without any suppressions applied. I don't think, this is currently supported. Suppressions are basically always enabled.
Forced disabling suppressions sounds like a useful enhancement for some cases. Although I wonder, how it can be handled practically - it might be, if you have a big project, you'll be overwhelmed if all violations/duplications are reported.

CPD Suppression is described here: https://pmd.github.io/latest/pmd_userdocs_cpd.html#suppression
If you are interested in how much this is used in your code base, you could simply grep for "CPD-OFF"/"CPD-ON" or "CPD-START"/"CPD-END".

[kloessst]

Thanks for your answer. We use static code analysis tools such as PMD in the context of programming exercises. We automatically assess student submissions by running tests and static code analysis tools. If there are options to circumvent violations, the students will find them 😄.
Theoretically, we could search for "CPD-OFF"/"CPD-ON" or "CPD-START"/"CPD-END" in student submissions and let them fail. Deactivating the suppressions with a configuration option would be much cleaner.