[
https://issues.apache.org/jira/browse/SLING-10992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17457732#comment-17457732
]
Konrad Windszus commented on SLING-10992:
-----------------------------------------
With the linked PR I see the following warning in Sling Starter 12-SNAPSHOT
{code}
*WARN* [pool-2-thread-1] org.apache.sling.jcr.contentloader.PathEntry Bundle
'org.apache.sling.sample.slingshot': Directive 'maven:mount' not supported in
header Sling-Initial-Content but it is used with value 'true'
{code}
This also affects Composum bundles. I don't find any references to directive
{{maven:mount}} but it is referenced in
https://github.com/apache/sling-samples/blob/master/slingshot/bnd.bnd.
Has this directive ever been evaluated?
> Emit warn in case Sling-Initial-Content header contains unknown directives or
> attributes
> ----------------------------------------------------------------------------------------
>
> Key: SLING-10992
> URL: https://issues.apache.org/jira/browse/SLING-10992
> Project: Sling
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: JCR ContentLoader 2.5.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> The Sling-Initial-Content header only supports some directives and no
> attributes at all according to the [common header
> grammar|https://docs.osgi.org/specification/osgi.core/7.0.0/framework.module.html#framework.common.header.syntax]
> and
> https://sling.apache.org/documentation/bundles/content-loading-jcr-contentloader.html#initial-content-loading.
> Pretty often directives and attributes are mixed up, therefore it would be
> good to emit a WARN for every unknown attribute or directive in that header.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
