[ https://issues.apache.org/jira/browse/TAMAYA-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213084#comment-16213084 ]
ASF subversion and git services commented on TAMAYA-300: -------------------------------------------------------- Commit ba9bea17824727915b688a28a6ff7e8fc62fd28e in incubator-tamaya-extensions's branch refs/heads/master from [~anatole] [ https://git-wip-us.apache.org/repos/asf?p=incubator-tamaya-extensions.git;h=ba9bea1 ] TAMAYA-300 Added temporal log entry to check a build issue. > 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)