[
https://issues.apache.org/jira/browse/SLING-11488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17570002#comment-17570002
]
Dominik Süß commented on SLING-11488:
-------------------------------------
[~Sc0rpic0m], [~kwin] here a suggestion - we could make this also be repoinit
yet being named differently - the configuration option would be about
redirecting which extension to use to consume repoinit - that way we can split
up the repoinit blocks into the scopes necessary and the converter can chose
which (0, 1, n named ones) extension to consume during the conversion - this
way we can easily add just the one necessary for the sdk jar (build time) and
keep the full repoinit for 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)
