You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org> on 2010/12/15 16:59:58 UTC

[jira] Closed: (MNG-3463) AsbtractMojo should look for LoggerManager plexus component

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

Benjamin Bentmann closed MNG-3463.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: Issues to be reviewed for 3.x)
                   2.0.9
         Assignee: Benjamin Bentmann

Looking at the {{DefaultPluginManager}}, the mojo logger is already delegating to a plexus logger since ages.

> AsbtractMojo should look for LoggerManager plexus component
> -----------------------------------------------------------
>
>                 Key: MNG-3463
>                 URL: http://jira.codehaus.org/browse/MNG-3463
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Logging
>            Reporter: Robert Egan
>            Assignee: Benjamin Bentmann
>             Fix For: 2.0.9
>
>
> AbstractMojo currently defines it's own Log interface, hard coded to use System.out. This really restricts the logging capabilities of all plugins. It would be nice if it attempted to look up the plexus role "org.codehaus.plexus.logging.LoggerManager" first and only used System.out if that failed.
> Doing this would also go a long way towards resolving MNG-2570 and MNG-3305.

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