Reduce log level of "no files to analyze" to INFO

[Bukama]

New feature, improvement proposal

Currently the message about "no files to analyze" is logged on Warning. This results in Warnings for projects which don't contain java files, e.g. Documentation as code projects.

Note: If you skip PMD in those you don't get the "no files to analyze" warning, but a "No files found to generate report on. Check if compile phase has been run"- which also occurs when PMD should be skip in report configuration. Also "skipEmptyReport" does not avoid this.

[adangel]

If there are no files to analyze, we probably should not execute PMD at all then.
So, just changing the log level in maven-pmd-plugin from warn to info (

maven-pmd-plugin/src/main/java/org/apache/maven/plugins/pmd/PmdReport.java

Line 382 in 7e1fbfe

getLog().warn("No files found to process. Did you forget to add additional source directories?"

) is not enough, as PMD itself will also log a warning ("No files to analyze. Check input paths and exclude parameters, use --debug to see file collection traces.")

Do you know, where "No files found to generate report on" comes from?

[Bukama]

If there are no files to analyze, we probably should not execute PMD at all then.

Also fine with that. My goal is to get rid of Warnings in build.

Do you know, where "No files found to generate report on" comes from?

Looks like our Jenkins summary listed this warning under PMD (maybe due multithreading log issue), but looking on a single threaded execution it seems origins from spotbugs. So not related to PMD

[Bukama]

We could also think about skipping the plugin based on the packaging type, e.g. a pom (or in Maven 4 bom) archive wont contain sources anyway. I would argue its the same for ear but not sure how people use this

[Bukama]

Looking at the code I see the additional check for language "java". Need to check this in my teams settings, when back from business track next week. But I think it still makes sense so skip the plugin