[
https://issues.apache.org/jira/browse/SLING-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17569992#comment-17569992
]
Dominik Süß commented on SLING-11488:
-------------------------------------
[~kwin] the challenge at hand is not specific to Adobe. The requirement here is
to be able to convert a package and bundles into something that can be layered
on top of a base that has a lifecycle independent from the application at hand.
Therefore the output of conversion should depend on some kind of uber API (in
the case of AEM this is sdk jar) which contains the stable contract that can be
analyzed against. As detected in the past the full repoinit such a layer would
use is containing too many moving bits that are unnecessary and distracting to
analyze so this is being stripped out - now repoinit does register namespaces
which are necessary to run the conversion from sling-initial-content into
content packages.
This ticket aims to make sure only the information necessary for the
transformation can be provided while omitting repoinit that is supposed to be
integrated and analyzed at a later time (deploy time).
> CPConverter - use extension "extracted-repo-namespaces"
> ---------------------------------------------------------
>
> Key: SLING-11488
> URL: https://issues.apache.org/jira/browse/SLING-11488
> Project: Sling
> Issue Type: Bug
> Components: Content-Package to Feature Model Converter
> Affects Versions: Content-Package to Feature Model Converter 1.1.14
> Reporter: Niek Raaijmakers
> Assignee: Niek Raaijmakers
> Priority: Major
>
> We at Adobe are introducing a new extension "extracted-repo-namespaces" in
> the aem SDK feature model.
> In here we put "register namespace repoinit statements" of the repository, so
> we can use the namespaces without issues.
> We need to use a separate extension with just the register namespace
> statements, instead of all the repoinit statements of the SDK, because then
> the aemanalyser will analyse a huge repoinit statement that is irrelevant for
> the end-users.
>
> But we do need the namespaces for sling initial content to work in the
> CPConverter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
