[
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158137#comment-16158137
]
Carsten Ziegeler commented on SLING-6868:
-----------------------------------------
With the new bundle resource implementation, you can use the following header
in the manifest:
{noformat}
SLING-INF/libs/sling/hapi/; path:=/libs/sling/hapi; overwrite:=true;
uninstall:=false;propsJSON:=json
{noformat}
With the "propsJSON" directive you tell the bundleresource implementation to
treat all files having the extension "json" (this is the value of propsJSON) as
JSON files containing a resource structure. Then your *.json files simply
contain the resource tree. Looking at the current "types.json" I think it will
work out of the box. You don't need the jcr.PrimaryType property anymore as
this is not stored in JCR.
> Initial content should 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 1.1.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.4.14#64029)
