[ 
https://issues.apache.org/jira/browse/NUTCH-3138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sebastian Nagel reassigned NUTCH-3138:
--------------------------------------

    Assignee: Sebastian Nagel

> Upgrade to Creadur RAT 0.17
> ---------------------------
>
>                 Key: NUTCH-3138
>                 URL: https://issues.apache.org/jira/browse/NUTCH-3138
>             Project: Nutch
>          Issue Type: Improvement
>          Components: build, dependency
>    Affects Versions: 1.22
>            Reporter: Sebastian Nagel
>            Assignee: Sebastian Nagel
>            Priority: Minor
>             Fix For: 1.23
>
>         Attachments: apache-rat-report.rat-0.16.txt, 
> apache-rat-report.rat-0.17.txt
>
>
> An upgrade to RAT 0.17 makes the GitHub workflow reporting an error because 
> of a changed RAT report format.
> We need to adapt the GitHub workflow to the new report format.
> However, the RAT 0.17 also reports errors:
> {noformat}
>     (Entries starting with '!' exceed the minimum or maximum values)
>   Approved:           925    A count of approved licenses.
>   Archives:           1    A count of archive files.
>   Binaries:           65    A count of binary files.
>   Document types:     4    A count of distinct document types.
>   Ignored:            0    A count of ignored files.
>   License categories: 2    A count of distinct license categories.
>   License names:      2    A count of distinct license names.
>   Notices:            5    A count of notice files.
>   Standards:          928    A count of standard files.
> ! Unapproved:         3    A count of unapproved licenses.
>   Unknown:            3    A count of unknown file types.
> {noformat}
> We might need to address these errors. The issue was uncovered together with 
> NUTCH-3137 / [PR#875|https://github.com/apache/nutch/pull/875].
> 0.16 and 0.17 RAT reports attached, both based on the upgraded dependencies 
> per NUTCH-3137.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to