[
https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090712#comment-15090712
]
Hervé Boutemy edited comment on MNG-5836 at 1/9/16 5:46 PM:
------------------------------------------------------------
Reopening the issue: I think Igor is right
our conf is sub-optimal: it makes us at risk (of such bad dependency) without
giving us any benefit
given a logging conf should be modifiable, putting it in a jar does not really
make sense (which is another way of saying "only the client has to do logging
configuration")
if nobody object, I'll do the IMHO good fix/improvement found by Igor
was (Author: hboutemy):
Reopening the issue: I think Igor is right
our conf is sub-optimal: it makes us at risk (of such bad dependency) without
giving us any benefit
given a logging conf should be modifiable, putting it in a jar does not really
make sense (which is another way of saying "only the client has to do logging
configuration")
if nobody object, I'll do the IMHO good fix found by Igor
> logging config is overwritten by $M2_HOME/lib/ext/*.jar
> -------------------------------------------------------
>
> Key: MNG-5836
> URL: https://issues.apache.org/jira/browse/MNG-5836
> Project: Maven
> Issue Type: Bug
> Reporter: Igor Fedorenko
>
> If one of the jars in {{$M2_HOME/lib/ext/*.jar}} happens to have
> {{simplelogger.properties}}, that configuration file masks logging
> configuration under {{$M2_HOME/conf/logging}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
