[
https://issues.apache.org/jira/browse/SLING-6868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158122#comment-16158122
]
Carsten Ziegeler commented on SLING-6868:
-----------------------------------------
[~andrei.dulvac] The currently released version of bundleresource does not have
this provide capability at all. So right now a bundle can't indicate that it
needs the bundleresource implementation at all.
With the new provided capability, bundles can indiate this -and then they just
need to require whatever version we use in the bundleresource capability.
The versioning should follow semantic versioning, therefore I changed the
provided version now to "1.1" which I believe is correct. The currently
released bundle provides version "1.0" (not supporting JSON), the new one is
compatible but adds JSON support on top. Therefore 1.1 is the correct version
> 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)
