You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2017/05/22 09:16:04 UTC

[jira] [Commented] (SLING-6868) Initial content should use more specific path or be migrated to bundle resources

    [ https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019339#comment-16019339 ] 

Carsten Ziegeler commented on SLING-6868:
-----------------------------------------

As these resources are static, I think it is even better to use bundle resources (using the Sling-Bundle-Resources) header. This way the resources are served directly from within the bundle and no content needs to be installed
[~andrei.dulvac]

> Initial content should use more specific path or be migrated to bundle resources
> --------------------------------------------------------------------------------
>
>                 Key: SLING-6868
>                 URL: https://issues.apache.org/jira/browse/SLING-6868
>             Project: Sling
>          Issue Type: Bug
>          Components: HApi
>    Affects Versions: HApi 1.0.0
>            Reporter: Carsten Ziegeler
>             Fix For: HApi 1.0.2, HApi 2.0.0
>
>
> Currently the initial content in the hapi bundle does not specify a path, which means it is using "/".
> When applied at the wrong time, it potentially could wipe the whole repository. In addition initial content should always be specified with the most specific path (the tree the bundle is owning)
> So the path is something like /libs/sling/hapi
> or even
> /libs/sling/hapi/components



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)