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

Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/06/13 04:03:12 UTC

[jira] Updated: (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 ]

Brett Porter updated MNG-3463:
------------------------------

    Fix Version/s: 2.1

> AsbtractMojo should look for LoggerManager plexus component
> -----------------------------------------------------------
>
>                 Key: MNG-3463
>                 URL: http://jira.codehaus.org/browse/MNG-3463
>             Project: Maven 2
>          Issue Type: Improvement
>          Components: Logging
>            Reporter: Robert Egan
>             Fix For: 2.1
>
>
> 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