[
https://issues.apache.org/jira/browse/SLING-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12646854#action_12646854
]
Bertrand Delacretaz commented on SLING-728:
-------------------------------------------
Giving priority to one path over another for installs looks easy, in
WatchedFolder.scan():
while(it.hasNext()) {
final Node n = it.nextNode();
// add code here: ignore this node if there's another one
// that "masks" it, from a folder with more priority
for(NodeConverter nc : converters) {
But handling deletes is a bit trickier, I assume that deleting a node in a
priority folder should cause the config defined by the non-priority folder node
to be reactivated.
> JcrInstall should prefer config in /apps/{xyz} over /libs/{xyz}
> ---------------------------------------------------------------
>
> Key: SLING-728
> URL: https://issues.apache.org/jira/browse/SLING-728
> Project: Sling
> Issue Type: Bug
> Components: JCR Install
> Affects Versions: JCR Install 2.0.4
> Reporter: Tobias Bocanegra
> Fix For: JCR Install 2.0.4
>
>
> currently jcrinstall does not respect the search paths correctly.
> the idea is, that configuration (and bundles) residing in /apps/{path} should
> win over /libs/{path}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
