[
https://issues.apache.org/jira/browse/SLING-10545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-10545.
--------------------------------------
Resolution: Fixed
Made the manifest optional in
https://github.com/apache/sling-org-apache-sling-feature-analyser/commit/8a9a8ca65b024e2f3335fe027c584bff2952d4d7
> 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)
