[
https://issues.apache.org/jira/browse/MPIR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728577#comment-17728577
]
Herve Boutemy commented on MPIR-445:
------------------------------------
{quote}In this case, I do see that the issue can move to the site plugin
{quote}
we got to the conclusion the message was written by the plugin run as goal,
then no, maven-site-plugin has nothing to do with it
{quote}We do care about unit test output. A far too often ignored principle of
TDD is that passing tests generate no output
{quote}
I do agree, even if I don't know how we can do it
First, I'll update the issue description, because that's really not obvious
that the issue is for plugins's build unit test output, not for normal
end-users using the plugin
Then ideas welcome on how to update the plugins's unit-test code to redirect
logging outside of System.out: I don't know if it's feasible or not
> Rendering content log junk
> --------------------------
>
> Key: MPIR-445
> URL: https://issues.apache.org/jira/browse/MPIR-445
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Reporter: Elliotte Rusty Harold
> Priority: Minor
>
> Another log message that's unneeded and simply clutters the output:
> [INFO] Rendering content with
> org.apache.maven.skins:maven-default-skin:jar:1.3 skin.
> Reduce to debug or remove completely.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
