August 2009 - logback-dev - mailman3.qos.ch

[JIRA] Created: (LBCLASSIC-108) LOGBack Classic Bundle does not declare ch.qos.logback.core.rolling as Import-Package
by Christian Brensing (JIRA) 18 Nov '09

18 Nov '09

LOGBack Classic Bundle does not declare ch.qos.logback.core.rolling as Import-Package ------------------------------------------------------------------------------------- Key: LBCLASSIC-108 URL: http://jira.qos.ch/browse/LBCLASSIC-108 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.15 Reporter: Christian Brensing Assignee: Logback dev list Priority: Minor The LOGBack Classic Bundle has no Import-Package for ch.qos.logback.core.rolling (and rolling.helper), resulting in a ClassNotFoundException when using e.g. the RollingFileAppender from the Core-Bundle. The ClassNotFoundException will be raised because the Bundle which initializes the LoggerContext (Classic) can not load the Appender from the Core-Bundle. The Bnd-Tool by Peter Kriens and the Maven-Felix-Plugin only detects package dependencies that are imported in java classes. Runtime dependencies like Appenders must be explicitly configured in the bnd-file or pom. This issue is identically to the one I reported for the SpringSource-Bundle-Repository, see https://issuetracker.springsource.com/browse/BRITS-165. -- 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

2 2

[JIRA] Created: (LBCLASSIC-149) ContextNameConverter does not use the context of the event
by Ceki Gulcu (JIRA) 13 Nov '09

13 Nov '09

ContextNameConverter does not use the context of the event ---------------------------------------------------------- Key: LBCLASSIC-149 URL: http://jira.qos.ch/browse/LBCLASSIC-149 Project: logback-classic Issue Type: Bug Reporter: Ceki Gulcu Assignee: Logback dev list ContextNameConverter instead of reading the context name found in the event passed as parameter, uses the context to which it (the ContextNameConverter instance) is attached to. Usually the two contexts are the same. However, when an event is sent to a remote server, the wrong information is displayed. -- 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

1 1

[JIRA] Created: (LBCORE-98) TimeBasedRollingPolicy: name of file in zip archive is <FileNamePattern>.nanos.tmp
by Anders Wallgren (JIRA) 13 Nov '09

13 Nov '09

TimeBasedRollingPolicy: name of file in zip archive is <FileNamePattern>.nanos.tmp ---------------------------------------------------------------------------------- Key: LBCORE-98 URL: http://jira.qos.ch/browse/LBCORE-98 Project: logback-core Issue Type: Bug Components: Rolling Affects Versions: 0.9.15 Environment: Windows Reporter: Anders Wallgren Assignee: Logback dev list Priority: Minor The name of the filename in the zip archive is a temp filename, based on the FileNamePattern, no the FileNamePattern itself. -- 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

2 4

[JIRA] Created: (LBCORE-101) OSGi manifest headers too restrictive
by david varnes (JIRA) 12 Nov '09

12 Nov '09

OSGi manifest headers too restrictive ------------------------------------- Key: LBCORE-101 URL: http://jira.qos.ch/browse/LBCORE-101 Project: logback-core Issue Type: Bug Affects Versions: 0.9.15 Reporter: david varnes Assignee: Logback dev list This issue is very similar and could be addressed at the same time as LBCLASSIC-119, LBCLASSIC-121 & LBCLASSIC-131. The Import-Package definition for logback-core requires that the javax.* packages be available at runtime. The pom.xml file and my usage seem to indicate that they should be optional. Attached patch adds javax.* as 'optional' in addition to the exiting janino declaration. thanks ! -- 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

2 2

[JIRA] Created: (LBCLASSIC-119) Missing Export-Package declarations in logback-classic OSGi bundle
by Pavol Juhos (JIRA) 08 Nov '09

08 Nov '09

Missing Export-Package declarations in logback-classic OSGi bundle ------------------------------------------------------------------ Key: LBCLASSIC-119 URL: http://jira.qos.ch/browse/LBCLASSIC-119 Project: logback-classic Issue Type: Bug Components: Other Affects Versions: 0.9.15 Environment: OSGi environment Reporter: Pavol Juhos Assignee: Logback dev list Priority: Critical logback-classic OSGi bundle doesn't export logback implementation packages. These packages need to be imported by bundles implementing custom logback Appenders etc. The problem is most likely caused a misconfiguration of maven-bundle-plugin in logback-classic POM. Current configuration: <instructions> <Export-Package>ch.qos.logback.classic.*</Export-Package> <Export-Package>org.slf4j.impl;version=1.5.6</Export-Package> <Import-Package>sun.reflect;resolution:=optional, javax.jms;resolution:=optional, * </Import-Package> <Bundle-RequiredExecutionEnvironment>J2SE-1.5</Bundle-RequiredExecutionEnvironment> </instructions> Suggested configuration: <instructions> <Export-Package>ch.qos.logback.classic.*, org.slf4j.impl;version=1.5.6 </Export-Package> <Import-Package>sun.reflect;resolution:=optional, javax.jms;resolution:=optional, * </Import-Package> <Bundle-RequiredExecutionEnvironment>J2SE-1.5</Bundle-RequiredExecutionEnvironment> </instructions> Second Export-Package declaration seems to override the first one. -- 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

2 1

Git as a version control system?
by Ceki Gulcu 22 Sep '09

22 Sep '09

Hi all, I was wondering if we should be moving to git as our version control system. I really like the fact that git's repository is stored on the local disk. It also appears that git makes it easier for developers to contribute patches. Could anybody confirm or care to share their experiences with git? Is there anyone against using git? BR -- Ceki Gülcü Logback: The reliable, generic, fast and flexible logging framework for Java. http://logback.qos.ch

6 24

Enable the JIRA RPC interface?
by david＠davidkarlsen.com 22 Sep '09

22 Sep '09

hi. Can you enable the RPC services for JIRA - that way it's possible to use Mylyn as a frontend. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com

2 1

[JIRA] Created: (LBCLASSIC-152) XMLLayout thread safety
by Darryl Smith (JIRA) 29 Aug '09

29 Aug '09

XMLLayout thread safety ----------------------- Key: LBCLASSIC-152 URL: http://jira.qos.ch/browse/LBCLASSIC-152 Project: logback-classic Issue Type: Bug Components: layout Affects Versions: 0.917 Reporter: Darryl Smith Assignee: Logback dev list XMLLayout assumes it is being called from a synchronized appender and uses shared StringBuilder buffer for creating the layout. Changes in http://jira.qos.ch/browse/LBCLASSIC-135 break that assumption -- 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

1 0

[JIRA] Created: (LBCLASSIC-150) allow for dynamic modificaton of a logging event
by Ceki Gulcu (JIRA) 24 Aug '09

24 Aug '09

allow for dynamic modificaton of a logging event ------------------------------------------------ Key: LBCLASSIC-150 URL: http://jira.qos.ch/browse/LBCLASSIC-150 Project: logback-classic Issue Type: New Feature Components: Other Affects Versions: 0.917 Reporter: Ceki Gulcu Assignee: Logback dev list It may be sometimes useful to dynamically change the level of a statement after an associated logging event is created. See for example the discussion on i18n: http://www.slf4j.org/pipermail/dev/2009-August/002500.html -- 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

1 0

Git
by Ralph Goers 23 Aug '09

23 Aug '09

I am working on LBCLASSIC-116 and should have working code for you in a couple of days. I've cloned the repository and am working on my Mac. So when it is ready how do I make it available for review?

2 1