Pull request is submitted but the build process seems buggy as my PR is not the only one failing currently
https://github.com/apache/logging-log4j2/pull/75 -----Ursprüngliche Nachricht----- Von: Michael Lück [mailto:michael.lu...@hm-ag.de] Gesendet: Montag, 24. April 2017 14:59 An: 'Log4J Users List' <log4j-user@logging.apache.org> Betreff: AW: AW: Trailing space on loglevel in properties file not trimmed Of course ... -----Ursprüngliche Nachricht----- Von: Remko Popma [mailto:remko.po...@gmail.com] Gesendet: Montag, 24. April 2017 14:57 An: Log4J Users List <log4j-user@logging.apache.org> Betreff: Re: AW: Trailing space on loglevel in properties file not trimmed Makes sense. Do you feel like submitting a patch or a pull request? (Shameless plug) Every main() method deserves http://picocli.info > On Apr 24, 2017, at 21:41, Michael Lück <michael.lu...@hm-ag.de> wrote: > > Yes you're right. Java.util.Properties work this way. But I think the > application that uses such properties should still validate the input. An > because the levels are a fixed set of values it would be good to trim them > after reading and before initializing the logger with the value. > > -----Ursprüngliche Nachricht----- > Von: Remko Popma [mailto:remko.po...@gmail.com] > Gesendet: Montag, 24. April 2017 14:38 > An: Log4J Users List <log4j-user@logging.apache.org> > Betreff: Re: Trailing space on loglevel in properties file not trimmed > > I believe that's how java.util.Properties work but I can imagine this can be > surprising... > > Remko > > (Shameless plug) Every main() method deserves http://picocli.info > >> On Apr 24, 2017, at 21:24, Michael Lück <michael.lu...@hm-ag.de> wrote: >> >> Hello all, >> >> >> >> I just realised that a trailing space on a level configuration in a >> properties file doesn’t change the level of the logger. >> >> I created a small example project >> https://github.com/thuri/log4j-trailing-space-loglevel-properties >> >> >> >> While the root logger is initialized with level info I want to make >> the custom logger for package com.github.thuri to log on level debug. >> >> >> >> When the level definition is written as >> >> „logger.logtest.level = DEBUG “ >> >> No Debug level logs occur on console >> >> >> >> When using >> >> “logger.logtest.level = DEBUG” >> >> It works as expected. >> >> >> >> Should it really work this way or is this a bug? >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org > For additional commands, e-mail: log4j-user-h...@logging.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-user-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-user-h...@logging.apache.org
