[
https://issues.apache.org/jira/browse/SLING-3037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759004#comment-13759004
]
Chetan Mehrotra commented on SLING-3037:
----------------------------------------
I can provide a patch as per suggestion in LOGBACK-384. It would involve
overriding the Logback class in our bundle i.e. placing a class of same name
and package in our bundle. Logback is under EPL ... so to check on legal front
would it be ok to override the class which has a different license compared to
ASL
> 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
>
>
> 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
