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

[jira] [Comment Edited] (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=16024427#comment-16024427 ] 

Andrei Dulvac edited comment on SLING-6868 at 5/25/17 9:03 AM:
---------------------------------------------------------------

[~cziegeler], from our talk offline - you're ok with this, right?


was (Author: andrei.dulvac):
[~cziegeler], from our talk offline - you're ok with this.

> 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
>            Assignee: Andrei Dulvac
>             Fix For: 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)