You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@creadur.apache.org by "Philipp Ottlinger (Jira)" <ji...@apache.org> on 2020/06/16 15:09:00 UTC

[jira] [Updated] (RAT-270) Output errors (and only errors) to console

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

Philipp Ottlinger updated RAT-270:
----------------------------------
    Affects Version/s: 0.13

> Output errors (and only errors) to console
> ------------------------------------------
>
>                 Key: RAT-270
>                 URL: https://issues.apache.org/jira/browse/RAT-270
>             Project: Apache Rat
>          Issue Type: Bug
>    Affects Versions: 0.13
>            Reporter: Elliotte Rusty Harold
>            Priority: Major
>
> From "the irony, it burns!" department, I bring you the Apache RAT error message extracted from several dozen pages of useless log junk:
> [ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.13:check (rat-check) on project maven-parent: Too many files with unapproved license: 1 See RAT report in: /home/jenkins/jenkins-slave/workspace/dehaus.plexus-plexus-utils-3.3.0/m/target/rat.txt -> [Help 1]
> This is why the build fails on Jenkins, but notice that the one piece of information needed to diagnose and fix the issue is not included in the output. And if there's any way to find this file on Jenkins, I couldn't figure out how. Nor is the problem reproducible locally.
> Rat can generate a text file if it wants, but it should output paths to files that fail the build to the console. That would be more useful than 99% of the log lines Maven vomits onto the screen. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)