[
https://issues.apache.org/jira/browse/SLING-5210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14982370#comment-14982370
]
David Bosschaert edited comment on SLING-5210 at 10/30/15 11:07 AM:
--------------------------------------------------------------------
The attached subsystem_base.zip contains an initial implementation and unit
tests for this. This is a new maven module that should go under
https://svn.apache.org/repos/asf/sling/trunk/installer/factories
was (Author: bosschaert):
The attached subsystem_base.zip contains an initial implementation for this.
This is a new maven module that should go under
https://svn.apache.org/repos/asf/sling/trunk/installer/factories
> Create an installer factory/transformer for slingstart-maven-plugin generated
> intermediary subsystem files
> ----------------------------------------------------------------------------------------------------------
>
> Key: SLING-5210
> URL: https://issues.apache.org/jira/browse/SLING-5210
> Project: Sling
> Issue Type: Task
> Components: Installer
> Reporter: David Bosschaert
> Attachments: subsystem_base.zip
>
>
> Because run modes determine the actual content deployed at runtime, the
> slingstart-maven-plugin cannot directly generate .esa files from the
> provisioning model. It generates an intermediary format which can be
> transformed into an subsystem .esa file at runtime once the current run modes
> are known. This JIRA is to generate the transformer to do this work at run
> time.
> More details on SLING-5149
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
