[
https://issues.apache.org/jira/browse/SLING-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17777624#comment-17777624
]
Stefan Seifert commented on SLING-12113:
----------------------------------------
with the improvement from
https://github.com/apache/sling-org-apache-sling-feature-cpconverter/pull/172
the new message will look like:
{noformat}
File content being unzipped is too big (>100 MB):
/jcr_root/apps/myapp/install/mybundle-1.0.0-SNAPSHOT.jar
{noformat}
> CPConverter: Improve error message "File being unzipped is too big" for
> Sling-Initial-Content
> ---------------------------------------------------------------------------------------------
>
> Key: SLING-12113
> URL: https://issues.apache.org/jira/browse/SLING-12113
> Project: Sling
> Issue Type: Improvement
> Components: Feature Model
> Affects Versions: Content-Package to Feature Model Converter 1.3.4
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.3.6
>
>
> if you use an OSGi bundle with Sling-Initial-Content, and the size of the
> unzipped content exceeds 100MB, currently an error messages without any
> context (out of a complex build) is issued:
> {noformat}
> Caused by: java.lang.IllegalStateException: File being unzipped is too big.
> at
> org.apache.sling.feature.cpconverter.handlers.slinginitialcontent.SlingInitialContentBundleEntryMetaDataCollector.collectFromContextAndWriteTmpFiles
> (SlingInitialContentBundleEntryMetaDataCollector.java:105)
> at
> org.apache.sling.feature.cpconverter.handlers.slinginitialcontent.BundleSlingInitialContentExtractor.extract
> (BundleSlingInitialContentExtractor.java:80)
> at
> org.apache.sling.feature.cpconverter.handlers.SlingInitialContentBundleHandler.processBundleInputStream
> (SlingInitialContentBundleHandler.java:53)
> at
> org.apache.sling.feature.cpconverter.handlers.BundleEntryHandler.handle
> (BundleEntryHandler.java:141)
> ...
> {noformat}
> this error messages should be improved to include the actual file name, and
> the actual limit that was hit (it's hard-coded 100MB in this case).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
