[
https://issues.apache.org/jira/browse/RAT-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136571#comment-17136571
]
Elliotte Rusty Harold commented on RAT-270:
-------------------------------------------
Maven should indeed reduce the amount of junk in the log but that's not what
I'm asking for (and not an issue for Rat in any case). I want more in the
console. Specifically I want the actual error Rat found. That's useful,
actionable information. There's no reason to dig through Jenkins build output
to locate it. It should be front and center, like anything else that causes the
build to fail.
This is one of several failing builds:
https://builds.apache.org/job/maven-box/job/maven-parent/job/dependabot%252Fmaven%252Forg.codehaus.plexus-plexus-utils-3.3.0/
> 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
> 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)
