[
http://jira.codehaus.org/browse/MSCMCHGLOG-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152536#action_152536
]
Emmanuel Hugonnet commented on MSCMCHGLOG-8:
--------------------------------------------
Thank you Benjamin, the logging problem was caused by the SCM API which uses
its own kind of logger (ScmLogger) and not the maven one (you need to go the
the maven-scm-plugin to have one implementation). I didn't understand why I was
getting the report traces but not my scm commands traces. I should have been
more carefull but I did the quick hack and used the JDK Logging API.
> 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
