[
https://issues.apache.org/jira/browse/MNG-5932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16997632#comment-16997632
]
Michael Osipov commented on MNG-5932:
-------------------------------------
The very first obstacle is that every logging framework has a different
approach to logging configuration. How shall we provide a unified configuration
for disjoint backends?
> Per-user and per-project logging configuration
> ----------------------------------------------
>
> Key: MNG-5932
> URL: https://issues.apache.org/jira/browse/MNG-5932
> Project: Maven
> Issue Type: Improvement
> Components: Logging
> Affects Versions: 3.3.3, 3.3.9
> Reporter: Brian Oxley
> Priority: Major
>
> It would be of much use to support per-user and per-project logging
> configuration. This supports cases where different projects have different
> maven logging requirements (e.g., post-processing maven output as part of a
> pipeline). Currently I need to change the maven installation to, for
> example, swap out logback for simplelogger, or to change the simplelogger
> settings.
> As a workaround on simplelogger I can use .mvn/jvm.config to pass system
> properties for simplelogger, but this is non-obvious and does not help with
> changing SLF4J implementation.
> I would like to be able to use something like .mvn/logging/<files here> akin
> to conf/logging under $M2_HOME and/or lib/ext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
