[ https://issues.apache.org/jira/browse/MNG-5836?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14573921#comment-14573921 ]
Igor Fedorenko commented on MNG-5836: ------------------------------------- Just to be clear, do you suggest that current order of m2.conf entries is correct and desirable? {code} [plexus.core] optionally ${maven.home}/lib/ext/*.jar load ${maven.home}/lib/*.jar load ${maven.home}/conf/logging {code} Can you elaborate why? I can't think of a case when having conf/logging as the last entry in the list is preferable. This is the place where users can change logging configuration, so I expect it to have highest priority regardless of of anything else present on classpath. For example, if conf/logging is the first entry, the logging library could provide default configuration, which the user would still be able override through explicit configuration. > 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)