You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/10/25 14:28:01 UTC

[jira] [Commented] (SLING-7752) Deserializing and serializing a feature model file suffles the configurations

    [ https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16663807#comment-16663807 ] 

ASF GitHub Bot commented on SLING-7752:
---------------------------------------

andreituicu 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-433072825
 
 
   @bosschaert Please let me know if there is anything more required here. Thank you!

----------------------------------------------------------------
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:
users@infra.apache.org


> 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 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)