[
https://issues.apache.org/jira/browse/SLING-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-11120.
--------------------------------------
Assignee: Carsten Ziegeler
Resolution: Fixed
https://github.com/apache/sling-org-apache-sling-servlets-resolver/commit/b3d4286b857df18b244b2446be95abaf1a6575b3
> Reduce log output from BundledScriptTracker
> -------------------------------------------
>
> Key: SLING-11120
> URL: https://issues.apache.org/jira/browse/SLING-11120
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Servlets Resolver 2.9.4
>
>
> With bundled scripts it might happen that a lot of warnings are outputted,
> like below. It's usually a capability that doesn't provide its own script,
> nor does it have a main script or selector script in the one from which it
> inherits.
> This can also happen if folders in libs hvae a sling:resourceSuperType on
> them without having scripts in the chain. Sometimes the reason for that is to
> trigger the Sling Resource Merger for a component dialog
> As this warning does not really provide something actionable but just fills
> the logs, we should reduce the log level to Debug.
> {noformat}
> 04.02.2022 09:30:43.427 *WARN* [FelixStartLevel]
> org.apache.sling.servlets.resolver.internal.bundle.BundledScriptTracker
> Unable to locate an executable for capability
> BundledRenderUnitCapability[sling.servlet.resourceTypes=[/libs/foo/templates/bar,
> foo/templates/bar]; extends=foo/myerviceconfigs/templates/configpage].
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
