[
https://issues.apache.org/jira/browse/SLING-7752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16521982#comment-16521982
]
ASF GitHub Bot commented on SLING-7752:
---------------------------------------
rombert 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-399868731
> 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?
If we're sure about what we want the version to be, we can skip the check
for a single release, e.g. `mvn release:prepare release:perform
-Darguments="-Dbaseline.skip=true"` . Not 100% sure about the exact syntax, but
that should get you started.
----------------------------------------------------------------
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)
