[
https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666420#comment-16666420
]
Carsten Ziegeler commented on SLING-7752:
-----------------------------------------
Commit 222c1bd02dfd4b4f54882e32e3584cb26cd92b40 broke all downstream users of
the Feature API as the properties changed from a Dictionary to a Map.
Furthermore, as ConfigurationAdmin is using a Dictionary, its preferable to
keep a Dictionary
> Deserializing and serializing a feature model file suffles the configurations
> -----------------------------------------------------------------------------
>
> Key: SLING-7752
> URL: https://issues.apache.org/jira/browse/SLING-7752
> Project: Sling
> Issue Type: Bug
> Components: Feature Model
> Reporter: Andrei Tuicu
> Priority: Major
> Fix For: Feature Model 0.1.4, Feature Model IO 0.1.4
>
>
> h3. Problem
> Deserializing and serializing a feature model file suffles the
> configurations. This happens, because unordered maps (HashMaps/Hashtables)
> are used in the implementations. The problem is relevant in the context of
> adding these files in code versioning systems, because a minor change to a
> file, done in an automated fashion, produces a big diff in the versioning
> system and it becomes very hard to see exactly what is the relevant change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
