You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (JIRA)" <ji...@apache.org> on 2018/03/16 22:40:17 UTC

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

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

Michael Osipov closed MNG-5394.
-------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results.

> Document how to do logging in a plugin
> --------------------------------------
>
>                 Key: MNG-5394
>                 URL: https://issues.apache.org/jira/browse/MNG-5394
>             Project: Maven
>          Issue Type: Task
>          Components: Logging
>         Environment: n/a
>            Reporter: Anders Hammar
>            Priority: Major
>
> 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|http://maven.apache.org/maven-logging.html]" 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
(v7.6.3#76005)