maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Herve Boutemy (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-5395) logger name for plugins should not be DefaultMavenPluginManager
Date Sat, 01 Dec 2012 08:09:14 GMT

    [ https://jira.codehaus.org/browse/MNG-5395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=314802#comment-314802
] 

Herve Boutemy commented on MNG-5395:
------------------------------------

I did a little local fix: the discussion on the global question (logger names, NDC, MDC, coding
conventions, actual code state, ...) still need to be done
but no need to stay in the actual bogus situation, this fix will be useful to better see the
actual code status
                
> logger name for plugins should not be DefaultMavenPluginManager
> ---------------------------------------------------------------
>
>                 Key: MNG-5395
>                 URL: https://jira.codehaus.org/browse/MNG-5395
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Plugin Requests
>    Affects Versions: 3.0.4
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: 3.1.0
>
>
> there are discussion about what should be the best name for every logger in Maven, which
hasn't come to a final decision yet.
> But waiting for the final choice, actual value is completely wrong: every plugin uses
the same logger that is the logger from DefaultMavenPluginManager
> In actual spirit, the value should be the mojo class name

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message