May 2017 - logback-dev - mailman3.qos.ch

[JIRA] (LOGBACK-1307) 1.3.0-SNAPSHOT is misspelled "SNAPSPHOT" in POMs
by QOS.CH (JIRA) 31 May '17

31 May '17

Richard Sand created LOGBACK-1307: ------------------------------------- Summary: 1.3.0-SNAPSHOT is misspelled "SNAPSPHOT" in POMs Key: LOGBACK-1307 URL: https://jira.qos.ch/browse/LOGBACK-1307 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.3.0 Reporter: Richard Sand Assignee: Logback dev list Priority: Trivial The POMs starting with the parent all have an extra 'P' in the word SNAPSHOT {{<version>1.3.0-SNAPSH{color:#d04437}*P*{color}OT</version>}} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1306) Detect logback.ContextSelector in System environment
by QOS.CH (JIRA) 30 May '17

30 May '17

Richard Sand created LOGBACK-1306: ------------------------------------- Summary: Detect logback.ContextSelector in System environment Key: LOGBACK-1306 URL: https://jira.qos.ch/browse/LOGBACK-1306 Project: logback Issue Type: Improvement Components: logback-classic Affects Versions: 1.3.0, 1.2.4 Environment: Any Reporter: Richard Sand Assignee: Logback dev list Attachments: ContextSelectorStaticBinder.patch We have a use case where it is very useful to allow ContextSelectorStaticBinder to discover the logback.ContextSelector from the environment properties as opposed to the System properties. It comes up when you have multiple apps running in the same container and need to specify an alternate ContextSelector for only one of the apps, whereas the System property would affect all apps (and the container itself). The patch is trivial and is attached to this issue. Basically, in ContextSelectorStaticBinder.init(), instead of: {{String contextSelectorStr = OptionHelper.getSystemProperty(ClassicConstants.LOGBACK_CONTEXT_SELECTOR);}} The patch does: {{String contextSelectorStr = OptionHelper.getEnv(ClassicConstants.LOGBACK_CONTEXT_SELECTOR);}} {{if (contextSelectorStr == null) \{}} {{ contextSelectorStr = OptionHelper.getSystemProperty(ClassicConstants.LOGBACK_CONTEXT_SELECTOR);}} {{}}} The patch can be applied to 1.2.4-SNAPSHOT (is that a thing?) or 1.3.0-SNAPSHOT, the ContextSelectorStaticBinder is the same in both. Thank you! -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1305) Logback-classic cannot be built by Eclipse m2e due to importing default package
by QOS.CH (JIRA) 30 May '17

30 May '17

Richard Sand created LOGBACK-1305: ------------------------------------- Summary: Logback-classic cannot be built by Eclipse m2e due to importing default package Key: LOGBACK-1305 URL: https://jira.qos.ch/browse/LOGBACK-1305 Project: logback Issue Type: Bug Components: logback-classic Affects Versions: 1.3.0 Environment: Eclipse Neon.3 (4.6.3) on Win2K8 64-bit Reporter: Richard Sand Assignee: Logback dev list Checked out Logback 1.3.0-SNAPSHOT into Eclipse Neon.3 (4.6.3). The other modules build OK but the classic module fails with the error: {{Error(s) found in manifest configuration (org.apache.felix:maven-bundle-plugin:2.5.4:manifest:bundle-manifest:process-classes)}}{{ org.apache.maven.plugin.MojoExecutionException: Error(s) found in manifest configuration}}{{ation}} {{ at org.apache.felix.bundleplugin.ManifestPlugin.execute(ManifestPlugin.java:84)}} The maven console shows the error: {{5/30/17, 10:58:11 AM EDT: [ERROR] Manifest ch.qos.logback:logback-classic:jar:1.3.0-SNAPSHPOT : The default package '.' is not permitted by the Import-Package syntax.}} {{This can be caused by compile errors in Eclipse because Eclipse creates }}{{valid class files regardless of compile errors.}} {{*{color:#d04437}The following package(s) import from the default package [ch.qos.logback.classic.gaffer]{color}* }} {{5/30/17, 10:58:11 AM EDT: [ERROR] Error(s) found in manifest configuration}} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-173) Log Rotation/Gzip process leaving .tmp files behind
by QOS.CH (JIRA) 30 May '17

30 May '17

1 0

[JIRA] (LOGBACK-1304) no log of error stack trace after implementing custom layout
by QOS.CH (JIRA) 30 May '17

30 May '17

1 0

[JIRA] (LOGBACK-1304) no log of error stack trace after implementing custom layout
by QOS.CH (JIRA) 29 May '17

29 May '17

arik olsh created LOGBACK-1304: ---------------------------------- Summary: no log of error stack trace after implementing custom layout Key: LOGBACK-1304 URL: https://jira.qos.ch/browse/LOGBACK-1304 Project: logback Issue Type: Bug Components: logback-core Environment: spring boot application, java. Reporter: arik olsh Assignee: Logback dev list after implementing a custom layout for logging using slf4j and logback for some reason the log does not support error stack trace. ...Exception e.. when I do log.error("",e); nothing is printed. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1303) Wrong delimiter in pattern layout for ISO 8601
by QOS.CH (JIRA) 26 May '17

26 May '17

Maxim Neverov created LOGBACK-1303: -------------------------------------- Summary: Wrong delimiter in pattern layout for ISO 8601 Key: LOGBACK-1303 URL: https://jira.qos.ch/browse/LOGBACK-1303 Project: logback Issue Type: Bug Components: logback-core Affects Versions: 1.2.3 Reporter: Maxim Neverov Assignee: Logback dev list The CoreConstants class contains the following: {code:java} public static final String ISO8601_PATTERN = "yyyy-MM-dd HH:mm:ss,SSS";{code} According to [https://www.w3.org/TR/NOTE-datetime] a decimal fraction of a second must be delimited by a dot, not comma. So the rigth pattern would be: {code:java} yyyy-MM-dd HH:mm:ss.SSS{code} -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-1302) Throwable is trimmed twice which causes bad message
by QOS.CH (JIRA) 24 May '17

24 May '17

1 0

[JIRA] (LOGBACK-1302) Throwable is trimmed twice which causes bad messge
by QOS.CH (JIRA) 22 May '17

22 May '17

Alex Khomchenko created LOGBACK-1302: ---------------------------------------- Summary: Throwable is trimmed twice which causes bad messge Key: LOGBACK-1302 URL: https://jira.qos.ch/browse/LOGBACK-1302 Project: logback Issue Type: Bug Components: logback-classic Environment: checkout at 0b94aad9c42771374e42e817a4c488af2bc6a2da Reporter: Alex Khomchenko Assignee: Logback dev list I've created 2 tests to show an issue and put them in PR. -- This message was sent by Atlassian JIRA (v7.3.1#73012)

1 0

[JIRA] (LOGBACK-995) Standalone rollover gets exception
by QOS.CH (JIRA) 19 May '17

19 May '17

1 0