[
https://issues.apache.org/jira/browse/LOG4J2-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662953#comment-15662953
]
Ralph Goers commented on LOG4J2-1686:
-------------------------------------
I assumed that because your original reply before you edited it mentioned a
LoggerSelector I have no idea the value of a LoggerSelector during
configuration would be as I con't think of anything useful it would do. If you
want to have different levels in dev than in prod then you could use properties
(i.e. - Lookups) for that.
The problem with what you are suggesting as that selectors don't necessarily
make sense across all configuration elements. I think we have implemented them
where they do but we are open to creating more if needed.
> Support conditional configuration
> ---------------------------------
>
> Key: LOG4J2-1686
> URL: https://issues.apache.org/jira/browse/LOG4J2-1686
> Project: Log4j 2
> Issue Type: New Feature
> Components: Configurators
> Affects Versions: 2.7
> Reporter: Raman Gupta
> Priority: Blocker
>
> It would be great to support conditional configuration like logback:
> http://logback.qos.ch/manual/configuration.html#conditional
> This allows for more advanced configuration than is currently possible with
> property substitution.
> Example use case: to implement
> https://issues.apache.org/jira/browse/LOG4J2-1685 without log4j library
> support.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
