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 2014/06/15 22:18:10 UTC

[jira] (MNG-5394) Document how to do logging in a plugin

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

Jason van Zyl commented on MNG-5394:
------------------------------------

I think we should just document using SLF4J using the static LoggerFactory and avoiding telling people to do anything else. SLF4J has been in there long enough now.

> Document how to do logging in a plugin
> --------------------------------------
>
>                 Key: MNG-5394
>                 URL: https://jira.codehaus.org/browse/MNG-5394
>             Project: Maven 2 & 3
>          Issue Type: Task
>          Components: Logging
>         Environment: n/a
>            Reporter: Anders Hammar
>
> We should document the different logging options in a Maven plugin that exist and differences/benefits. So the main audience is not Maven users, but plugin developers and I guess this doc should go in under the Plugin Developer Center section.
> There is currently a "Maven 3.1.x logging" page, but that one is for end users and a different story than what this ticket is about.
> A few things that the page should cover:
> * Plexus logger & SLF4J
> * Any compatibility problems using SLF4J with older Maven versions?
> * A code example including an example pom depicting dependencies
> * How to establish logging separated from Maven's (fork a JVM?)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)