[ https://issues.apache.org/jira/browse/SLING-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759153#comment-13759153 ]
Chetan Mehrotra edited comment on SLING-3037 at 9/5/13 3:18 PM: ---------------------------------------------------------------- Patch which locally overrides the ch.qos.logback.classic.util.LoggerNameUtil with fix included as per comment by Chris in LOGBACK-384. The fix is also provided to Logback as per [1]. Untill it gets included we can override the LoggerNameUtil in Sling log bundle [1] http://jira.qos.ch/browse/LOGBACK-384?focusedCommentId=13483&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13483 was (Author: chetanm): Patch which locally overrides the ch.qos.logback.classic.util.LoggerNameUtil with fix included as per comment by Chris in LOGBACK-384 > IllegalArgumentException in logback Logger > ------------------------------------------ > > Key: SLING-3037 > URL: https://issues.apache.org/jira/browse/SLING-3037 > Project: Sling > Issue Type: Bug > Components: Engine > Affects Versions: Scripting Core 2.0.24 > Reporter: Bertrand Delacretaz > Assignee: Bertrand Delacretaz > Fix For: Scripting Core 2.0.26 > > Attachments: SLING-3037.patch > > > Since switching to logback in SLING-2024, a number of integration tests are > failing, typical stack trace: > java.lang.IllegalArgumentException: > For logger [apps.integration-test] child name > [apps.integration-test.srt$1378284549103 passed as parameter, may not include > '.' after index22 > at ch.qos.logback.classic.Logger.createChildByName(Logger.java:357) > at > ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:143) > at ch.qos.logback.classic.LoggerContext.getLogger(LoggerContext.java:45) > at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:253) > at > org.apache.sling.scripting.core.impl.DefaultSlingScript.verifySlingBindings(DefaultSlingScript.java:676) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira