- logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-788) ch.qos.logback.core.ConsoleAppender imports unused "org.fusesource.jansi.WindowsAnsiOutputStream"
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 0

[JIRA] (LOGBACK-787) ch.qos.logback.classic.db.DBAppender - potential null pointer access
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 0

[JIRA] (LOGBACK-786) ch.qos.logback.classic.gaffer.NestedType is refused by Groovy 2
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 0

[JIRA] (LOGBACK-785) Potential Null Pointer Access in ch.qos.logback.classic.joran.action.ConsolePluginAction
by David Tonhofer (JIRA) 01 Jan '13

01 Jan '13

1 0

[JIRA] (LOGBACK-783) Support for compressing logfiles with bzip2
by Daniel Serodio (JIRA) 27 Dec '12

27 Dec '12

3 3

[JIRA] (LOGBACK-784) SyslogAppender atomic stacktrace writing
by Juergen Weber (JIRA) 27 Dec '12

27 Dec '12

1 0

[JIRA] Created: (LBCORE-52) Make SyslogAppenderBase fields protected
by Anton Tagunov (JIRA) 27 Dec '12

27 Dec '12

Make SyslogAppenderBase fields protected ---------------------------------------- Key: LBCORE-52 URL: http://jira.qos.ch/browse/LBCORE-52 Project: logback-core Issue Type: Improvement Reporter: Anton Tagunov Assignee: Logback dev list Hi! We'd like to customize some of SyslogAppender. Since SyslogAppenderBase class is public and is a base class by destination would it be appropriate to have all of the fields be designated as 'protected'? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

3 5

[qos-ch/logback-contrib] f9209d: mongo-java-driver should not have as scope 'provid...
by Christian Trutz 22 Dec '12

22 Dec '12

Branch: refs/heads/master Home: https://github.com/qos-ch/logback-contrib Commit: f9209dc77cb91258022a9ff4a1f823e7c49291fd https://github.com/qos-ch/logback-contrib/commit/f9209dc77cb91258022a9ff4a1… Author: Christian Trutz <christian.trutz(a)belaso.de> Date: 2012-12-22 (Sat, 22 Dec 2012) Changed paths: M README.md M pom.xml Log Message: ----------- mongo-java-driver should not have as scope 'provided'. Signed-off-by: Christian Trutz <christian.trutz(a)belaso.de>

1 0

Versioning logback-contrib
by Christian Trutz 22 Dec '12

22 Dec '12

Hi Tony, I propose to use following workflow to version logback-contrib: 1) we don't use SNAPSHOT 2) if a version is "in work", it gets the version of the following next release 3) if a release is ready, we tag this version in GIT For example: - Version v_0.1.1 is ready: git tag -a v_0.1.1 - In pom.xml we have version 0.1.2 - many development iterations - Version v_0.1.2 is ready: git tag -a v_0.1.2 ... OK? Christian 2012/12/20 Tony Trinh <tony19(a)gmail.com> > Branch: refs/heads/master > Home: https://github.com/qos-ch/logback-contrib > Commit: cdc7faa03d32b37da39e64ba8a10d8a2359d256b > > https://github.com/qos-ch/logback-contrib/commit/cdc7faa03d32b37da39e64ba8a… > Author: Tony Trinh <tony19(a)gmail.com> > Date: 2012-12-19 (Wed, 19 Dec 2012) > > Changed paths: > M pom.xml > > Log Message: > ----------- > Add SNAPSHOT label to version > > > Commit: 74dca95fb9432f96dae2ef4707ebc44d8885cc81 > > https://github.com/qos-ch/logback-contrib/commit/74dca95fb9432f96dae2ef4707… > Author: Tony Trinh <tony19(a)gmail.com> > Date: 2012-12-19 (Wed, 19 Dec 2012) > > Log Message: > ----------- > Merge branch 'master' into fixbr > > > Commit: 082e705d09b557ac69eb77dfc7e6d6f59b31a4ed > > https://github.com/qos-ch/logback-contrib/commit/082e705d09b557ac69eb77dfc7… > Author: Tony Trinh <tony19(a)gmail.com> > Date: 2012-12-19 (Wed, 19 Dec 2012) > > Changed paths: > M eclipse/pom.xml > M jackson/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 > > Log Message: > ----------- > [maven-release-plugin] prepare release v_0.1.2 > > > Compare: > https://github.com/qos-ch/logback-contrib/compare/262b20f15678...082e705d09… > > _______________________________________________ > logback-dev mailing list > logback-dev(a)qos.ch > http://mailman.qos.ch/mailman/listinfo/logback-dev >

3 4

Failing tests when building v1.0.9
by Bruno Penteado 21 Dec '12

21 Dec '12

I am trying to build the v1.0.9 of the project to make a hot fix for the issue LOGBACK-782 on my fork while v_1.0.10 is not released yet: git clone https://github.com/qos-ch/logback.git cd logback git checkout v_1.0.9 mvn clean test Im getting tests failures on the core module: testDay(ch.qos.logback.core.util.TimeUtilTest): expected:<1164078000000> but was:<1164074400000> testWeek(ch.qos.logback.core.util.TimeUtilTest): expected:<1164596400000> but was:<1164592800000> testMonth(ch.qos.logback.core.util.TimeUtilTest): expected:<1164942000000> but was:<1164938400000> testVaryingNumberOfDailyPeriods(ch.qos.logback.core.rolling.helper.RollingCalendarTest): p=13 expected:<1224381600000> but was:<1224385200000> If it is relevant, I am running the project on a mac If this is not a know issue and need more information, let me know Thanks, Bruno "Polaco"

1 1