felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FELIX-4844) Store configuration data in a diff-tool friendly way
Date Sat, 25 Apr 2015 09:57:38 GMT

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

Marcel Offermans commented on FELIX-4844:

ConfigurationAdmin offers a method to create a new configuration with a pre-defined service.pid
so I don't see your problem. In fact, the ability to create a configuration for a service.pid
(regardless of whether the associated service exists or not) was one of the use cases of the
specification. So making an import/export like bundle (similar to File Installer) is probably
your best option. That way you don't depend on any implementation detail.

> 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

View raw message