[
https://issues.apache.org/jira/browse/RAT-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18032268#comment-18032268
]
Gary D. Gregory edited comment on RAT-508 at 10/22/25 9:56 PM:
---------------------------------------------------------------
Hi [~pottlinger]
I appreciate your POV, and I've heard the same types of arguments from other
tooling authors (Maven plugins and others) and the reasons are similar "We must
say this and that because it matters!". But it's not usually the case. I'll
review my POV:
"users increase to the latest release version but do not always adapt their
configuration"
So what? It only matters for deprecations as I've stated above: "Warnings for
deprecations are OK of course."
"this excessive log output helps in finding out what to do as a consumer"
It doesn't unless you provide precise instructions and that only matters for
deprecations, which are OK to log IMO.
I don't need the logging to repeat what the configuration says in the POM,
that's the most egregious offense IMO.
"how did you go forward when you started to migrate to RAT0.17 - did you
consult the documentation and set logging to DEBUG?"
For a private project, I consulted the docs, and they were incomplete. The only
obvious replacement to replace <excludes> with <inputExcludes>. After that I
looked at
[https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html]
and it looks like it uses deprecated elements.
was (Author: garydgregory):
Hi [~pottlinger]
I appreciate your POV, and I've heard the same types of arguments from other
tooling authors (Maven plugins and others) and the reasons are similar "We must
say this and that because it matters!". But it's not usually the case. I'll
review my POV:
"users increase to the latest release version but do not always adapt their
configuration"
So what? It only matters for deprecations as I've stated above: "Warnings for
deprecations are OK of course."
"this excessive log output helps in finding out what to do as a consumer"
It doesn't unless you provide precise instructions and that only matters for
deprecations, which are OK to log IMO.
I don't need the logging to repeat what the configuration says in the POM,
that's the most egregious offense IMO.
"how did you go forward when you started to migrate to RAT0.17 - did you
consult the documentation and set logging to DEBUG?"
For a private project, I consulted the docs, and they were incomplete. The only
obvious replacement to replace <exclude> with <inputExclude>. After that I
looked at
[https://creadur.apache.org/rat/apache-rat-plugin/examples/custom-license.html]
and it looks like it uses deprecated elements.
> Maven plugin 0.17 logs way too much at the INFO level
> -----------------------------------------------------
>
> Key: RAT-508
> URL: https://issues.apache.org/jira/browse/RAT-508
> Project: Apache Rat
> Issue Type: Bug
> Components: Client - maven
> Affects Versions: 0.17
> Reporter: Gary D. Gregory
> Priority: Major
> Fix For: 1.0.0
>
>
> The new plugin 0.17 logs way to much at the INFO, for example, using
> commons-parent:
> {noformat}
> [INFO] --- apache-rat:0.17:check (rat-check) @ commons-parent ---
> [WARNING] Parameter 'excludes' is deprecated: Deprecated for removal since
> 0.17: Use <inputExclude> instead.
> [WARNING] Basedir is : /Users/garygregory/git/commons-parent
> [WARNING] Use of deprecated option 'exclude'. Deprecated for removal since
> 0.17: Use <inputExclude> instead.
> [INFO] Excluding patterns: site-content/**, .checkstyle, .fbprefs, .pmd,
> .asf.yaml, .gitattributes, src/site/resources/download_*.cgi,
> maven-eclipse.xml, .externalToolBuilders/**, .vscode/**, .project,
> .classpath, .settings/**, **/*.svg, **/*.xcf
> [INFO] Excluding MAVEN collection.
> [INFO] Excluding ECLIPSE collection.
> [INFO] Excluding IDEA collection.
> [INFO] Processing exclude file from STANDARD_SCMS.
> [INFO] Excluding STANDARD_SCMS collection.
> [INFO] Excluding MISC collection.
> [INFO] Excluding HIDDEN_DIR collection.
> [INFO] RAT summary:
> [INFO] Approved: 12
> [INFO] Archives: 0
> [INFO] Binaries: 1
> [INFO] Document types: 4
> [INFO] Ignored: 8
> [INFO] License categories: 1
> [INFO] License names: 1
> [INFO] Notices: 4
> [INFO] Standards: 12
> [INFO] Unapproved: 0
> [INFO] Unknown: 0
> [INFO]
> {noformat}
> You're telling me the same thing more than once is different ways.
> You're telling irrelevant information (Unknown: 0)
> Here is an example of helpful logging in comparison:
> {noformat}
> [INFO] --- artifact:3.6.1:check-buildplan (check-buildplan) @ commons-parent
> ---
> [INFO] No known issue in 17 plugins
> [INFO]
> {noformat}
> I suggest all of this logging is done at the debug level and make the output
> a single line like the {{check-buildplan}} example.
> It gets worse at the site level:
> {noformat}
> [INFO] Generating "RAT Report" report --- apache-rat-plugin:0.17:rat
> [WARNING] Basedir is : /Users/garygregory/git/commons-parent
> [WARNING] Use of deprecated option 'exclude'. Deprecated for removal since
> 0.17: Use <inputExclude> instead.
> [INFO] Excluding patterns: site-content/**, .checkstyle, .fbprefs, .pmd,
> .asf.yaml, .gitattributes, src/site/resources/download_*.cgi,
> maven-eclipse.xml, .externalToolBuilders/**, .vscode/**
> [INFO] Excluding MAVEN collection.
> [INFO] Excluding ECLIPSE collection.
> [INFO] Excluding IDEA collection.
> [INFO] Processing exclude file from STANDARD_SCMS.
> [INFO] Excluding STANDARD_SCMS collection.
> [INFO] Excluding MISC collection.
> [INFO] Excluding HIDDEN_DIR collection.
> [WARNING] Duplicate LicenseFamily category: AL (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: BSD-3 (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: CDDL1 (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: GPL (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: MIT (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: OASIS (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: W3C (action: IGNORE)
> [WARNING] Duplicate LicenseFamily category: W3CD (action: IGNORE)
> [WARNING] Duplicate License Apache License 1.0 (AL1.0) of type AL (action:
> IGNORE)
> [WARNING] Duplicate License Apache License 1.1 (AL1.1) of type AL (action:
> IGNORE)
> [WARNING] Duplicate License Apache License 2.0 (AL2.0) of type AL (action:
> IGNORE)
> [WARNING] Duplicate License BSD 3 clause (BSD-3) of type BSD-3 (action:
> IGNORE)
> [WARNING] Duplicate License DOJO License (DOJO) of type BSD-3 (action: IGNORE)
> [WARNING] Duplicate License The Telemanagement Forum License (TMF) of type
> BSD-3 (action: IGNORE)
> [WARNING] Duplicate License COMMON DEVELOPMENT AND DISTRIBUTION LICENSE
> Version 1.0 (CDDL1) of type CDDL1 (action: IGNORE)
> [WARNING] Duplicate License ILLUMOS CDDL1 Derived license (ILLUMOS) of type
> CDDL1 (action: IGNORE)
> [WARNING] Duplicate License GNU General Public License V1.0 (GPL1) of type
> GPL (action: IGNORE)
> [WARNING] Duplicate License GNU General Public License V2.0 (GPL2) of type
> GPL (action: IGNORE)
> [WARNING] Duplicate License GNU General Public License V3.0 (GPL3) of type
> GPL (action: IGNORE)
> [WARNING] Duplicate License The MIT License (MIT) of type MIT (action:
> IGNORE)
> [WARNING] Duplicate License OASIS Open License (OASIS) of type OASIS (action:
> IGNORE)
> [WARNING] Duplicate License W3C Software Copyright (W3C) of type W3C
> (action: IGNORE)
> [WARNING] Duplicate License W3C Document Copyright (W3CD) of type W3CD
> (action: IGNORE)
> [INFO] Excluding MISC collection.
> [INFO] Excluding HIDDEN_DIR collection.
> {noformat}
> NOTHING should be output, like all other plugins, for example:
> {noformat}
> [INFO] Rendering 16 report documents
> [INFO] Generating "Changes" report ---
> maven-changes-plugin:3.0.0-M3:changes
> [INFO] Generating "JIRA Report" report ---
> maven-changes-plugin:3.0.0-M3:jira-changes
> mvn [INFO] Generating "About" report ---
> maven-project-info-reports-plugin:3.9.0:index
> [INFO] Generating "Summary" report ---
> maven-project-info-reports-plugin:3.9.0:summary
> [INFO] Generating "Source Code Management" report ---
> maven-project-info-reports-plugin:3.9.0:scm
> [INFO] Generating "Issue Management" report ---
> maven-project-info-reports-plugin:3.9.0:issue-management
> [INFO] Generating "Mailing Lists" report ---
> maven-project-info-reports-plugin:3.9.0:mailing-lists
> [INFO] Generating "Maven Coordinates" report ---
> maven-project-info-reports-plugin:3.9.0:dependency-info
> [INFO] Generating "Dependency Management" report ---
> maven-project-info-reports-plugin:3.9.0:dependency-management
> [INFO] Generating "Dependency Convergence" report ---
> maven-project-info-reports-plugin:3.9.0:dependency-convergence
> [INFO] Generating "CI Management" report ---
> maven-project-info-reports-plugin:3.9.0:ci-management
> [INFO] Generating "Distribution Management" report ---
> maven-project-info-reports-plugin:3.9.0:distribution-management
> [INFO] Generating "Surefire" report ---
> maven-surefire-report-plugin:3.5.4:report
> {noformat}
> If every plugin goes down this verbose by default mode, Maven console output
> is useless.
> The ONLY output should be
> {noformat}
> [INFO] Generating "RAT Report" report --- apache-rat-plugin:0.17:rat
> {noformat}
> Warnings for deprecations are OK of course.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
