You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jason van Zyl (JIRA)" <ji...@codehaus.org> on 2009/12/27 18:56:56 UTC
[jira] Commented: (MNG-1175) Investigate if MavenEmbedderLogger can
be replaced by ...plugin.logging.Log
[ http://jira.codehaus.org/browse/MNG-1175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204197#action_204197 ]
Jason van Zyl commented on MNG-1175:
------------------------------------
There are already too many logging APIs, in the future we'll just use the SLF4J interace and inject the logger like any other component.
> Investigate if MavenEmbedderLogger can be replaced by ...plugin.logging.Log
> ---------------------------------------------------------------------------
>
> Key: MNG-1175
> URL: http://jira.codehaus.org/browse/MNG-1175
> Project: Maven 2 & 3
> Issue Type: Task
> Components: Embedding
> Reporter: Eugene Kuleshov
> Assignee: Jason van Zyl
> Priority: Critical
> Fix For: 3.x
>
>
> Maven plugins are using its own logging framework ...plugin.logging.Log which is quite the same as MavenEmbedderLogger exposed by embedder. Please investigate if plugin logger should be used directly.
> That could be helpful if some of IDE plugins would use maven plugins directly (e.g. some utility classes from maven-eclipse-plugin)
--
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