[
http://jira.codehaus.org/browse/MSCMCHGLOG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152484#action_152484
]
Benjamin Bentmann commented on MSCMCHGLOG-8:
--------------------------------------------
bq. how do you get a logger when unit testing ?
The maven-plugin-api provides a
{{[SystemStreamLog|http://maven.apache.org/ref/current/maven-plugin-api/apidocs/org/apache/maven/plugin/logging/SystemStreamLog.html]}}.
That can either be injected into the component under test by the test
controller or the component itself can return this if no other logger has been
set before (c.f. impl of {{AbstractMojo.getLog()}}).
> Plugin produces too much log at INFO level while analyzing log messages
> -----------------------------------------------------------------------
>
> Key: MSCMCHGLOG-8
> URL: http://jira.codehaus.org/browse/MSCMCHGLOG-8
> Project: Maven 2.x SCM Changelog Plugin
> Issue Type: Improvement
> Components: Report / Mojo
> Affects Versions: 1.0
> Environment: scmchangelog 1.0
> Reporter: Stevo Slavic
> Assignee: Emmanuel Hugonnet
> Priority: Minor
> Fix For: 1.1
>
> Attachments: scmchangelog-maven-plugin-analyseloglevel.patch
>
>
> While analyzing scm log messages scmchangelog plug-in unnecessarily produces
> a log message per scm log entry at what I think is too high, INFO, level.
> These log messages maybe would be interesting while debugging, but not in
> normal use of plug-in. Since Java Logging API is being used, I propose these
> messages to be logged at most at FINE level. Attached is a patch which makes
> necessary changes.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
