[ 
https://issues.apache.org/jira/browse/GUACAMOLE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769562#comment-16769562
 ] 

Michael Jumper commented on GUACAMOLE-734:
------------------------------------------

The original text of the issue also mentions a bug which would only affect the 
Logback build ("DatePatternToRegexTest fails on non English locale"). Given the 
way the original text was generically worded (plural despite single library, no 
specific reference to actual issues encountered in practice), the way half the 
issues were not relevant, the way the wrong repository was noted, and the 
remaining issues likely have zero impact on users of Guacamole, I suspect this 
issue was created by an automated bot without any real human checking.

Updating logback to the latest sounds like a good thing to do. Other than that, 
I don't think the original issue as it stood made much sense.

> Update logback-classic version
> ------------------------------
>
>                 Key: GUACAMOLE-734
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-734
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-client
>            Reporter: Kaifeng Huang
>            Assignee: Nick Couchman
>            Priority: Trivial
>
> The version of logback-classic currently referenced by the guacamole 
> {{pom.xml}} is relatively old and should be updated to the latest version, 
> assuming doing so does not break logging. There are bug reports associated 
> with the 1.1.2 version currently used by Guacamole, however it's unlikely 
> that those bugs actually have any impact on Guacamole users:
> || Issue || Description ||
> | [LOGBACK-1008|https://jira.qos.ch/projects/LOGBACK/issues/LOGBACK-1008] | 
> ConfigurationDelegate.groovy should check AppenderAttachable not 
> AsyncAppender |
> | [LOGBACK-1054|https://jira.qos.ch/projects/LOGBACK/issues/LOGBACK-1054] | 
> NullPointerException from RollingFileAppender |



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to