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-5396) logger name for execution events should not be MavenCli
Date Sat, 01 Dec 2012 08:42:13 GMT

     [ https://jira.codehaus.org/browse/MNG-5396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Herve Boutemy closed MNG-5396.
------------------------------

       Resolution: Fixed
    Fix Version/s: 3.1.0
         Assignee: Herve Boutemy

fixed in [1062524b| http://git-wip-us.apache.org/repos/asf/maven/commit/1062524b]
                
> logger name for execution events should not be MavenCli
> -------------------------------------------------------
>
>                 Key: MNG-5396
>                 URL: https://jira.codehaus.org/browse/MNG-5396
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: Logging
>    Affects Versions: 3.0.4
>            Reporter: Herve Boutemy
>            Assignee: Herve Boutemy
>             Fix For: 3.1.0
>
>
> actually, a lot of Maven output is done with MavenCli logger even 3 times the code executed
is not in MavenCli. See the MavenCli code:
> 1. CLIReportingUtils.showErrors
> 2. ExecutionEventLogger
> 3. getBatchTransferListener()
> If it can make sense to have the first one reporting with MavenCli logger name, the 2
formers whould better be with their own logger: this would ease filtering

--
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