- announce - mailman3.qos.ch

Release of logback version 1.1.3
by QOS.ch annoucements 24 Mar '15

24 Mar '15

Hello all, The logback team is happy to announce the release of logback version 1.1.3. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Release of SLF4J version 1.7.8
by QOS.ch annoucements 14 Dec '14

14 Dec '14

Hello all, I am happy to announce the immediate availability of SLF4J version 1.7.8 which can automatically detect and report mismatches between the class where a logger is defined and the logger name. For more details on this feature see: http://www.slf4j.org/codes.html#loggerNameMismatch The relevant artifacts should hit the Maven central repository within the next few hours. Please refer to the the news page for more details on this release: http://www.slf4j.org/news.html I am grateful to Matt Bishop for managing the SLF4J project in the last few months and in particular for handling the various pull requests submitted on github. This release would not have been possible without his help. The logger name mismatch detection mechanism, an exciting and new feature introduced in this release, was contributed by Alexander Dorokhine. I join the undoubtedly many SLF4J users in thanking Alexander for his great work. The 1.7.x series: The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. The 1.7.x series adds varargs support in Logger methods. Compared to previous versions, 1.7.5 significantly improves logger retrieval times. Users are highly encouraged to migrate to SLF4J 1.7.5 or later. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J binding can cause problems. For example, if you are using slf4j-api-1.7.1.jar, then you should also use slf4j-simple-1.7.1.jar, using slf4j-simple-1.5.5.jar will not work. From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. At initialization time, if SLF4J suspects that there may be an api vs. binding version mismatch problem, it will emit a warning about the suspected mismatch. Version 1.7.x series takes compatibility one step further so that slf4j-api and SLF4J bindings can be freely mixed with artifacts from the 1.6.x or 1.7.x series. In other words, when running under JDK 1.5 or later, version 1.7.x is totally 100% no-ifs-or-buts compatible with the 1.6.x series. Downloading SLF4J: You can download SLF4J, including full source code, class files and documentation on our download page: http://www.slf4j.org/download.html Announcement mailing list: You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki

1 0

ch.qos.logback.core.rolling.TimeBasedRollingPolicy writes a new log in the rolled over log
by QOS.ch annoucements 02 Sep '14

02 Sep '14

Team, My logback.xml is as follows: *<appender name="SIFT" class="ch.qos.logback.classic.sift.SiftingAppender">** ** <sift>** ** <appender name="FILE-Application" class="ch.qos.logback.core.rolling.RollingFileAppender">** **<file>log/application/application.log</file>** ** <rollingPolicy class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">** ** ** **<fileNamePattern>log/application/application.log.%d{yyyyMMdd}</fileNamePattern>** ** </rollingPolicy>** ** <encoder>** ** <pattern>%date %X{req.remoteHost} %X{sessionID} %X{userIDCookie} %X{userEmailID} %X{req.requestURI} %level %logger{10} %msg%n</pattern>** ** </encoder>** ** </appender> ** ** </sift>** **</appender>** ** **<root level="debug">** ** <appender-ref ref="SIFT" />** **</root>* My log4j.properties is as follows: *### direct log messages to stdout ###** **log4j.appender.stdout=org.apache.log4j.ConsoleAppender** **log4j.appender.stdout.Target=System.out** **log4j.appender.stdout.layout=org.apache.log4j.PatternLayout** **log4j.appender.stdout.layout.ConversionPattern=%d{MMM-dd@HH:mm:ss} %5p %c{1}:%L - %m%n** ** **### set log levels - for more verbose logging change 'info' to 'debug' ###** **log4j.rootLogger=debug, stdout** **log4j.logger.org.apache.commons.beanutils.BeanUtils=WARN ** **log4j.logger.org.apache.commons.beanutils.ConvertUtils=WARN ** **log4j.logger.org.apache.commons.beanutils.PropertyUtils=WARN ** **log4j.logger.org.apache.commons.beanutils.PropertyUtilsBean=WARN * I have a problem where the roller over log writes the new log in it. For example, Lets keep on Sep 1 2014 log is written in application.log and on the midnight the application.log.20140901 is rolled back and new log is still written in both application.log.20140901 and application.log.. Then on September 02 midnight the application.log.20140902 is created and new logs on September 3 is written in both application.log and application.log.20140902.., this way logs rolled back is writing the new logs in them.Thus the application.log.20140901has logs of September 02 and application.log.20140902 as logs on September 03. I am using the 1.0.13 version of logback jar. My app server is resin-3.0.22, web server is apache-2.2.22 and java version is jdk-1.5. Please can you answer why this issue happens?? Thanks, Shiva Ranjith .R

1 0

Release of logback version 1.1.2
by QOS.ch annoucements 02 Apr '14

02 Apr '14

Hello all, The logback team is happy to announce the release of logback version 1.1.2. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Release of SLF4J version 1.7.6
by QOS.ch annoucements 05 Feb '14

05 Feb '14

Hello all, I am happy to announce the immediate availability of SLF4J version 1.7.6, a maintenance release. The 1.7.x series adds varargs support in Logger methods. Compared to previous versions, 1.7.5 significantly improves logger retrieval times. Users are highly encouraged to migrate to SLF4J 1.7.5 or later. The relevant artifacts should hit the Maven central repository within the next few hours. The Simple Logging Facade for Java or (SLF4J) serves as a simple facade or abstraction for various logging frameworks, e.g. java.util.logging, log4j and logback, allowing the end user to plug in the desired logging framework at deployment time. Binary compatibility: Mixing mixing different versions of slf4j-api.jar and SLF4J binding can cause problems. For example, if you are using slf4j-api-1.7.1.jar, then you should also use slf4j-simple-1.7.1.jar, using slf4j-simple-1.5.5.jar will not work. From the client's perspective all versions of slf4j-api are compatible. Client code compiled with slf4j-api-N.jar will run perfectly fine with slf4j-api-M.jar for any N and M. You only need to ensure that the version of your binding matches that of the slf4j-api.jar. You do not have to worry about the version of slf4j-api.jar used to compile a given dependency in your project. You can always use *any* version of slf4j-api.jar, and as long as the version of slf4j-api.jar and its binding match, you should be fine. At initialization time, if SLF4J suspects that there may be an api vs. binding version mismatch problem, it will emit a warning about the suspected mismatch. Version 1.7.x series takes compatibility one step further so that slf4j-api and SLF4J bindings can be freely mixed with artifacts from the 1.6.x or 1.7.x series. In other words, when running under JDK 1.5 or later, version 1.7.x is totally 100% no-ifs-or-buts compatible with the 1.6.x series. Release notes: Please refer to the the news page for precise details. http://www.slf4j.org/news.html You can download SLF4J, including full source code, class files and documentation on our download page, shown below. http://www.slf4j.org/download.html Announcement mailing list: You can receive SLF4J related announcements by subscribing to the SLF4J announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter: https://twitter.com/qos_ch Enjoy, -- Ceki 65% of statistics are made up on the spot

1 0

Release of logback version 1.1.0
by QOS.ch annoucements 29 Jan '14

29 Jan '14

Hello all, The logback team is happy to announce the release of logback version 1.1.0. It contains many bug fixes and improvements. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Release of logback version 1.0.13
by QOS.ch annoucements 10 May '13

10 May '13

Hello all, I am happy to announce the release of logback version 1.0.13, a maintenance release containing only bug fixes and no new features. It should hit the Maven central repository by the time you read this message. Please refer to the news page for precise details about this release. http://logback.qos.ch/news.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter by following: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Release of logback version 1.0.12
by QOS.ch annoucements 26 Apr '13

26 Apr '13

Hello all, I am happy to announce the release of logback version 1.0.12. It should hit the Maven central repository within the next few hours. Please refer to the news page for precise details of this release. http://logback.qos.ch/news.html You can download logback, including full source code, class files and documentation on our download page, shown below. http://logback.qos.ch/download.html You can receive logback related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce You may also receive announcements via twitter via the following account: https://twitter.com/qos_ch Enjoy, -- Ceki Gülcü

1 0

Release of CAL10N v0.8.1
by QOS.ch annoucements 13 Apr '13

13 Apr '13

Hello all, Only a day after 0.8, I am happy to announce the availability of cal10n version 0.8.1 which reverts an backward incompatible change introduced in 0.8. Please avoid version 0.8, instead use 0.8.1 or later. Compiler Assisted Localization, abbreviated as CAL10N (pronounced as "calion") is a java library for writing localized (internationalized) messages. It supports java compiler verification of message keys used in source code and tooling to detect errors in message keys. The 0.8.x series brings support for JSR-269 annotation processors. In other words, verification of bundles can be performed at compilation time. For details see the documentation at: http://cal10n.qos.ch/manual.html#jsr269 You can download CAL10N, including full source code, class files and documentation on our download page, shown below. http://cal10n.qos.ch/download.html You can receive CAL10N related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki 65% of statistics are made up on the spot

1 0

Release of CAL10N v0.8
by QOS.ch annoucements 12 Apr '13

12 Apr '13

Hello all, I am happy to announce the immediate availability of cal10n version 0.8. This release adds JSR-269 support. In other words, verification of bundles can be performed at compilation time. For details see the documentation at: http://cal10n.qos.ch/manual.html#jsr269 Compiler Assisted Localization, abbreviated as CAL10N (pronounced as "calion") is a java library for writing localized (internationalized) messages. It supports java compiler verification of message keys used in source code and tooling to detect errors in message keys. You can download CAL10N, including full source code, class files and documentation on our download page, shown below. http://cal10n.qos.ch/download.html You can receive CAL10N related announcements by subscribing to the QOS.ch announce mailing list. To subscribe to QOS.ch announce list, please visit the following URL. http://www.qos.ch/mailman/listinfo/announce Enjoy, -- Ceki 65% of statistics are made up on the spot

1 0