[
https://issues.apache.org/jira/browse/SLING-4799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581744#comment-14581744
]
Bertrand Delacretaz commented on SLING-4799:
--------------------------------------------
[[email protected]] mentions the following workaround to force the
slingstart plugin to use the old format:
{code}
<plugin>
<groupId>org.apache.sling</groupId>
<artifactId>slingstart-maven-plugin</artifactId>
<extensions>true</extensions>
<version>1.2.0</version>
<dependencies>
<dependency>
<groupId>org.apache.felix</groupId>
<artifactId>org.apache.felix.configadmin</artifactId>
<version>1.8.4</version>
</dependency>
</dependencies>
</plugin>
{code}
> ConfigAdmin format for multi values has changed, clarify the impact
> -------------------------------------------------------------------
>
> Key: SLING-4799
> URL: https://issues.apache.org/jira/browse/SLING-4799
> Project: Sling
> Issue Type: Task
> Components: Launchpad
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> SLING-4793 introduces a change in the installer core to support a new format
> for loading and saving OSGi configs from files, where multi values use an
> improved but different format.
> An example failure scenario is given below, and we might have other similar
> issues with Crankstart and in upgrade scenarios - we need to find out more
> about those potential issues.
> Failure scenario:
> * I create a Sling Launchpad using the latest slingstart plugin
> * The provisioning model includes configs with multi values
> * The provisioning model includes an installer core bundle that is "too old"
> * Configs with multi values will then be ignored
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
