[
https://issues.apache.org/jira/browse/SLING-6196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919689#comment-16919689
]
Konrad Windszus edited comment on SLING-6196 at 8/30/19 4:21 PM:
-----------------------------------------------------------------
I would strongly recommend to either delete the one in Sling or put the one
from Sling in our Starter. What kind of signal is that if we trust external
bundles more than the Sling ones? What speaks against focussing the development
effort to the one being maintained at Sling?
Also if I compare
https://github.com/apache/sling-org-apache-sling-installer-factory-packages/blob/master/src/main/java/org/apache/sling/installer/factory/packages/impl/PackageTransformer.java
with
https://github.com/ist-dresden/composum/blob/develop/sling/core/pckginstall/src/main/java/com/composum/sling/core/pckginstall/PackageTransformer.java
I see that the Sling one is slightly more advanced. There have been some
improvements already and others are still open:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Installer%20Packages%20Factory%201.0.0%22
was (Author: kwin):
I would strongly recommend to either delete the one in Sling or put the one
from Sling in our Starter. What kind of signal is that if we trust external
bundles more than the Sling ones? What speaks against focussing the development
effort to the one being maintained at Sling?
> Add an OSGi Installer factory for content packages
> --------------------------------------------------
>
> Key: SLING-6196
> URL: https://issues.apache.org/jira/browse/SLING-6196
> Project: Sling
> Issue Type: Sub-task
> Components: General
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
