[
https://issues.apache.org/jira/browse/RAT-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17898963#comment-17898963
]
Claude Warren commented on RAT-98:
----------------------------------
[~sebb]
We have several outputs and where they go are very much dependant upon the UI
you are using and what options you have set.
||Output||CLI||Maven||Ant||Option||
|Log|System.out|Maven log|Ant log| <none>|
|Report|System.out|rat.txt in target directory|System.out|--output-file|
In the case of CI usage I believe that it captures the Maven/Ant log and prints
it to System.out so that it is visible after run.
The Report is generated from an XML file. If we pump the skipped file names
into the XML file I am concerned that it will become rather large and several
of the custom XSLT file I have seen would require that most of the file be in
memory to process.
Suppose we create the skipped log and have it work as follows:
By default no output.
--output-exclude-log (without an argument) will output to System.out
--output-exclude-log <file> will write the output to the specified file.
> Maven RAT report does not document skipped files
> ------------------------------------------------
>
> Key: RAT-98
> URL: https://issues.apache.org/jira/browse/RAT-98
> Project: Apache Rat
> Issue Type: Bug
> Reporter: Sebb
> Priority: Major
> Fix For: 0.17
>
>
> The Maven RAT report should document which files have been skipped using the
> <exclude> option.
> Either by listing the configuration details, or better by listing the file
> names with a marker, e.g. EX to show they were deliberately skipped.
> Note: this only refers to files listed in <exclude> entries, not files which
> are excluded by default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
