[
https://issues.apache.org/jira/browse/SLING-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12805845#action_12805845
]
Bertrand Delacretaz commented on SLING-1334:
--------------------------------------------
The additional logging is as follows, at the DEBUG level:
FolderNameFilter getPriority(/libs/sling/install)=100
Indicates that path priority was computed without taking run modes into account
(as the path does not contain dots)
FolderNameFilter getPriority(/libs/cq/security/config.author)=101
(prefix=/config, run modes=[author])
Indicates that parts of the path were considered in run mode based priority
computation.
I have also lowered the level of the "Not recursing into..." messages to DEBUG.
> Jcrinstall should log folder priority values for troubleshooting
> ----------------------------------------------------------------
>
> Key: SLING-1334
> URL: https://issues.apache.org/jira/browse/SLING-1334
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
> Priority: Minor
> Fix For: JCR Installer 3.0.2
>
>
> JcrInstaller.findPathsUnderNode(...) uses priorities computed by the
> FolderNameFilter to decide whether to watch a folder or not.
> Those priorities should be logged at the DEBUG level, for troubleshooting
> cases where it's unclear why a folder is not watched.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
