[
https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521460#comment-16521460
]
ASF GitHub Bot commented on SLING-7752:
---------------------------------------
bosschaert commented on issue #2: SLING-7752 - Deserializing and serializing a
feature model file suffles the configurations
URL:
https://github.com/apache/sling-org-apache-sling-feature/pull/2#issuecomment-399745758
Hi @andreituicu, after seeing the request to also change the Configurator
Code in Felix I thought a little more about this... Would it be possible to
implement a fix for SLING-7752 without the need to have ordering in the
configurator? I put my concerns about changing that one at
https://github.com/apache/felix/pull/144
Sorry for being a little difficult, but I think requiring that change to the
configurator makes for a brittle system...
Another thought could be to use a TreeMap instead of the LinkedHashMap here
in the feature model. That would mean that the keys will always be
alphabetically sorted, and would ultimately also resolve SLING-7752 I think.
On the BW compatibility plugin and it not considering 0.x versions
separately. I'm not sure how to deal with that. @rombert would you have an idea
about this?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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
>
> 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)
