[
https://issues.apache.org/jira/browse/SLING-3814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084448#comment-14084448
]
Chetan Mehrotra commented on SLING-3814:
----------------------------------------
bq. Do you really need to embed the groovy-all dependency? IIRC installing
groovy-all is enough to activate Groovy scripting in general, so why not just
expect it to be present?
The Groovy dependency would then need to be resolved at Start Level 1 which
would cause issue with existing setup where Groovy would be running at higher
level. Further embedding Groovy would also isolate logging dependencies from
others as Groovy bundle has a Dynamic-Import for * which causes it to be
refreshed often.
> Groovy fragment bundle for Common Log to support scriptable event evaluation
> ----------------------------------------------------------------------------
>
> Key: SLING-3814
> URL: https://issues.apache.org/jira/browse/SLING-3814
> Project: Sling
> Issue Type: New Feature
> Components: Extensions
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Attachments:
> org.apache.sling.extensions.logback-groovy-fragment-1.0.0-SNAPSHOT-src.zip
>
>
> Logback provides support for scriptable event evaluation [1] where a script
> can be used to determine if the given logging event must be logged or not.
> This proves useful to get precise logs in a concurrent env. For this Logback
> support
> * Janino - Allow writing Java Code and is faster compared to Groovy. Due to
> [LOGBACK-1001|http://jira.qos.ch/browse/LOGBACK-1001] it cannot be used
> currently
> * Groovy
> Commons Log bundle can have optional dependency on Groovy classes but that
> would cause issues as Commons Log starts at level 1 and further for stability
> of Logging system it would be preferable if it gets its own copy of Groovy
> (via a fragement).
> This feature is mostly to be used for debugging issues
> [1] http://logback.qos.ch/manual/filters.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
