You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Simone Tripodi (JIRA)" <ji...@apache.org> on 2019/07/09 14:38:00 UTC
[jira] [Commented] (SLING-8569) Detect & reports PackageTypes and
nesting structures during conversion
[ https://issues.apache.org/jira/browse/SLING-8569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881266#comment-16881266 ]
Simone Tripodi commented on SLING-8569:
---------------------------------------
[~dsuess] initial implementation on https://github.com/apache/sling-org-apache-sling-feature-cpconverter/tree/SLING-8569 feature branch
> Detect & reports PackageTypes and nesting structures during conversion
> ----------------------------------------------------------------------
>
> Key: SLING-8569
> URL: https://issues.apache.org/jira/browse/SLING-8569
> Project: Sling
> Issue Type: New Feature
> Components: Content-Package to Feature Model Converter
> Reporter: Dominik Süß
> Assignee: Simone Tripodi
> Priority: Major
>
> To be able to support legacy deployment structures that mixed (initial & permission) content and application packages with application packages the converter should generate an analysis of the originally passed packages in a file reporting the following information:
> * For each passed file report the nesting structures (including the paths within the hosting packages) including multilevel nesting
> * For each found package & subpackage detect & report the Package Type (Application, Mixed, Content)
> ** this should be detected from scratch as the optionally declared property is not reliable (might be a false declaration)
> ** detectionlogic should follow filevault semantics (https://github.com/apache/jackrabbit-filevault/blob/6df76ba4a45316a84ec1cd10636296d191a82260/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/io/AbstractExporter.java#L374-L399) but consider the type of nested packages - the jackrabbit implementation currently doesn't analyze subpackages but considers those as "content" as they are defined in "/etc"
> This report should allow to detect any package that (either directly or in its nested containers) contains content (nothing in apps & libs) and indicate the location within the original package (potentially also requiring unpacking multiple nesting levels).
> //[~simone.tripodi]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)