- logback-dev - mailman3.qos.ch

Code complexity survey
by Vard Antinyan 27 Sep '16

27 Sep '16

Dear logback developers, We have undertaken a task to assess code complexity triggers and generate recommendations for developing understandable code. Our intension is to share the results with you, developers, so everyone can learn the triggers behind complex software. We need your help for rigorous results. My request to you is - if you get 5-10 min. time, would you please consider to answer the questions of this survey on code complexity? https://goo.gl/forms/h9WXZ8VSEw7BUyHg1 You are welcome to learn preliminary results through this link: https://www.facebook.com/SoftwareCodeQuality/photos/?tab=album&album_id=163… The results will be shared in a public webpage and everyone possible will be invited to learn and discuss them. Your knowledge and experience is vital for achieving substantial and generalizable results, and your effort is much appreciated! Sincerely Vard Antinyan PhD candidate in University of Gothenburg, Sweden Tel: 0046317725707

1 0

[JIRA] (LOGBACK-1210) Typo in log message
by Gili (JIRA) 20 Sep '16

20 Sep '16

1 0

[JIRA] (LOGBACK-900) Tests failing
by Maxim Neverov (JIRA) 20 Sep '16

20 Sep '16

1 0

[Interesting Issue] - User defined logback configuration file for multiple WARS
by Shivaram A 15 Sep '16

15 Sep '16

Hello All Here is an interesting logback issue. I have logback used in my already existing project. These logback configuration files are externalized to tomcat server. The project consists of multiple web modules and each of these have respective logbacks like logback-PROJ1.xml, logback.PROJ2.xml etc and these are working completely fine. As per logback specification, logback configuration file should be defined as logback.xml or logback-test.xml. It is surprising that logs are generated on above defined custom naming conventions. I did check all the logback.Configuration set up etc but there are no values indeed. Please help me how can this work. Is there any other way that this code is working correctly. I am trying to implement a new module on this project and now its not working for me. I am using tomcat6.0

1 0

Logback doesn't write to a log file
by Sara J 24 Aug '16

24 Aug '16

Hello, I am trying to migrating my code from log4j to logback without changing my code using log4j-over-slfj.jar The logger files creates successefully but nothing is written in the log files/console *I added the following dependencies in my pom file:* <dependency> <groupId>org.slf4j</groupId> <artifactId>slf4j-api</artifactId> <version>1.7.21</version> </dependency> <dependency> <groupId>org.slf4j</groupId> <artifactId>log4j-over-slf4j</artifactId> <version>1.7.21</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-core</artifactId> <version>1.1.7</version> </dependency> <dependency> <groupId>ch.qos.logback</groupId> <artifactId>logback-classic</artifactId> <version>1.1.7</version> </dependency> *This is my logback.xml:* <?xml version="1.0" encoding="UTF-8"?> <configuration debug="true"> <property name="USER_HOME" value="c:\\temp" /> <property name="ENV_PREFIX" value="s1" /> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender">  <encoder> <pattern>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</pattern> </encoder> </appender> <appender name="COM_FILE" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${USER_HOME}\comFile-${ENV_PREFIX}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>${USER_HOME}\comFile-${ENV_PREFIX}.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>5</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>50MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%d [%t] %-3p - ID:%X{UUID} %m%n</pattern> </encoder> </appender> <appender name="ASYNC_COM_FILE" class="ch.qos.logback.classic.AsyncAppender"> <appender-ref ref="COM_FILE" /> </appender> <appender name="transactionLoggerData" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>${USER_HOME}\transaction-${ENV_PREFIX}.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>${USER_HOME}\transaction-${ENV_PREFIX}.%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>3</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy"> <maxFileSize>50MB</maxFileSize> </triggeringPolicy> <encoder> <pattern>%d [%t] %-3p - ID:%X{UUID} %m%n</pattern> </encoder> </appender> <appender name="ASYNC_TRAN_Logger" class="ch.qos.logback.classic.AsyncAppender"> <appender-ref ref="transactionLoggerData" /> </appender> <logger name="transactionLogger" level="INFO" additivity="false"> <appender-ref ref="ASYNC_TRAN_Logger" /> </logger> <logger name="FILE" level="INFO" additivity="false"> <appender-ref ref="ASYNC_COM_FILE" /> </logger> <root> <level value="INFO"/> <appender-ref ref="STDOUT" /> <appender-ref ref="FILE" /> </root> </configuration> *And I am specifying the location of the configuration file before logback is loaded:* System.setProperty("logback.configurationFile", fileName); InputStream inputStream = new FileInputStream(fileName); LoggerContext loggerContext = (LoggerContext) LoggerFactory .getILoggerFactory(); loggerContext.reset(); JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(loggerContext); configurator.doConfigure(inputStream); // loads logback file inputStream.close(); Could you please help? thanks, Sara

1 0

[qos-ch/logback-contrib] 840815: Update README.md
by Tony Trinh 11 Jun '16

11 Jun '16

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: 840815390966f72d9c6c2014674e57c25ea0d163 https://github.com/qos-ch/logback-contrib/commit/840815390966f72d9c6c201467… Author: Tony Trinh <tony19(a)gmail.com> Date: 2016-06-11 (Sat, 11 Jun 2016) Changed paths: M README.md Log Message: ----------- Update README.md

1 0

[qos-ch/logback-contrib] 0e0b72: [maven-release-plugin] prepare for next developmen...
by Tony Trinh 10 Jun '16

10 Jun '16

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: 0e0b72eb959959722556db59f46514fd01bdac0d https://github.com/qos-ch/logback-contrib/commit/0e0b72eb959959722556db59f4… Author: Tony Trinh <tony19(a)gmail.com> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M eclipse/pom.xml M jackson/pom.xml M janino-fragment/pom.xml M json/access/pom.xml M json/classic/pom.xml M json/core/pom.xml M json/pom.xml M mongodb/access/pom.xml M mongodb/classic/pom.xml M mongodb/core/pom.xml M mongodb/pom.xml M pom.xml M xmpp/pom.xml Log Message: ----------- [maven-release-plugin] prepare for next development iteration

1 0

[qos-ch/logback-contrib]
by tony19 10 Jun '16

10 Jun '16

Branch: refs/tags/v_0.1.5 Home: https://github.com/qos-ch/logback-contrib

1 0

[qos-ch/logback-contrib] f56560: Specify release-sign-artifacts profile in release....
by Tony Trinh 10 Jun '16

10 Jun '16

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: f565605b29bec5888f7c9224bb4df17394d2c9c4 https://github.com/qos-ch/logback-contrib/commit/f565605b29bec5888f7c9224bb… Author: Tony Trinh <tony19(a)gmail.com> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M release.sh Log Message: ----------- Specify release-sign-artifacts profile in release.sh The artifacts are only signed when the `release-sign-artifacts` profile is activated, which is normally done by the maven-release-plugin for the release:perform task. That's not happening for some reason, so as a workaround, we're now explicitly setting the profile when using the release script. We're soon switching to Gradle, so no further effort will be put in to fix this in Maven configs. This patch also allows passing mvn arguments to release.sh, which is useful for setting -DdryRun=true. Commit: 4176e79bae17dcf5377b7e373414bc1161c0ea2f https://github.com/qos-ch/logback-contrib/commit/4176e79bae17dcf5377b7e3734… Author: Tony Trinh <tony19(a)gmail.com> Date: 2016-06-10 (Fri, 10 Jun 2016) Changed paths: M eclipse/pom.xml M jackson/pom.xml M janino-fragment/pom.xml M json/access/pom.xml M json/classic/pom.xml M json/core/pom.xml M json/pom.xml M mongodb/access/pom.xml M mongodb/classic/pom.xml M mongodb/core/pom.xml M mongodb/pom.xml M pom.xml M xmpp/pom.xml Log Message: ----------- [maven-release-plugin] prepare release v_0.1.5 Compare: https://github.com/qos-ch/logback-contrib/compare/39cd5a5f975e...4176e79bae…

1 0

[qos-ch/logback-contrib] 39cd5a: Update README.md
by Tony Trinh 06 Jun '16

06 Jun '16

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: 39cd5a5f975ee64cd3d35f6184e48c00fea326b9 https://github.com/qos-ch/logback-contrib/commit/39cd5a5f975ee64cd3d35f6184… Author: Tony Trinh <tony19(a)gmail.com> Date: 2016-06-05 (Sun, 05 Jun 2016) Changed paths: M README.md Log Message: ----------- Update README.md

1 0