You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tamaya.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/10/01 12:25:02 UTC

[jira] [Commented] (TAMAYA-300) Provide a Tamaya integration module for OSGI ConfigAdmin

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

ASF subversion and git services commented on TAMAYA-300:
--------------------------------------------------------

Commit c990e961142fa66cb50a020217da3c84684546c1 in incubator-tamaya-sandbox's branch refs/heads/master from [~anatole]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-sandbox.git;h=c990e96 ]

TAMAYA-300 Simplified dependencies.


> Provide a Tamaya integration module for OSGI ConfigAdmin
> --------------------------------------------------------
>
>                 Key: TAMAYA-300
>                 URL: https://issues.apache.org/jira/browse/TAMAYA-300
>             Project: Tamaya
>          Issue Type: New Feature
>          Components: Sandbox
>            Reporter: Anatole Tresch
>            Assignee: Anatole Tresch
>            Priority: Critical
>             Fix For: 0.4-incubating
>
>
> Provide a functionality to extend/override/adapt any ConfigAdmin configuration as follows:
> * add new config entries
> * update (override) existing entries
> * remove entries (full synch)
> Hereby the dynamics of OSGI must be considered:
> * Removing Tamaya must recover the previous state.
> * It must be possible to enable/disable Tamaya Configuration by default on bundles by Tamaya bundle config or system properties.
> * It must be possible to selectively enable bundles for Tamaya configuration using Manifest entries.
> *  It must be possible to selectively control the override (op) mode for bundles using Manifest entries.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)