You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "A. J. David Bosschaert (Jira)" <ji...@apache.org> on 2021/06/29 08:18:00 UTC

[jira] [Closed] (SLING-10545) Make manifest for content packages optional

     [ https://issues.apache.org/jira/browse/SLING-10545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

A. J. David Bosschaert closed SLING-10545.
------------------------------------------

> Make manifest for content packages optional
> -------------------------------------------
>
>                 Key: SLING-10545
>                 URL: https://issues.apache.org/jira/browse/SLING-10545
>             Project: Sling
>          Issue Type: Improvement
>          Components: Feature Model Analyser
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: Feature Model Analyser 1.3.28
>
>
> The scanner for a content package always tries to parse the manifest, however if that manifest is invalide (which seems to be quiet common), then the scanner fails with an IOException.
> As the manifest is unusable anyway - but for most analysers not needed, it should gracefully ignore the exception and return null instead of the manifest



--
This message was sent by Atlassian Jira
(v8.3.4#803005)