[jira] [Comment Edited] (FELIX-4844) Store configuration data in a diff-tool friendly way

["Balazs Zsoldos (JIRA)" <ji...@apache.org>]

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

Balazs Zsoldos edited comment on FELIX-4844 at 4/25/15 10:10 AM:
-----------------------------------------------------------------

[~marrs] You mean I can create a configuration via the ConfigurationAdmin interface where I can specify the service.factoryPid with a pre-generated service.pid?


was (Author: balazs.zsoldos):
You mean I can create a configuration via the ConfigurationAdmin interface where I can specify the service.factoryPid with a pre-generated service.pid?

> Store configuration data in a diff-tool friendly way
> ----------------------------------------------------
>
>                 Key: FELIX-4844
>                 URL: https://issues.apache.org/jira/browse/FELIX-4844
>             Project: Felix
>          Issue Type: Wish
>          Components: Configuration Admin
>            Reporter: Balazs Zsoldos
>
> We store our configuration with the sources in the source-code control system (git). It often happens that multiple developers work on the same project and they modify the configuration parallel. It would not be a problem if the config files were diff-tool friendly. To achieve this goal, two improvements would be necessary:
> *Store entries in alphabetically ordered list*
> In the config files, the entries should be stored sorted by ABC. It is easy to implement by overriding HashTable in the same way that LinkedHashMap overrides HashMap.
> *Store array values in multiple lines*
> At the moment a setting with two values are stored like this:
> key=["value1", "value2"]
> Instead of this, I would store it in the following format (each entry on new line):
> key=[ \
>   "value1", \
>   "value2" \
>   ]
> *Question*
> Do you think that if I prepare a patch for this, that would be accepted?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)