Re: [DS/SCR] Configuration Binding

Hello Felix, On Aug 12, 2013, at 7:52 AM, Felix Meschberger fmesc...@adobe.com wrote: Currently our Declarative Services implementation statically binds configuration to the using bundle when such configuration is used to configure a component. The intent was to follow the Configuration

Re: Unable to administer Felix JIRA with latest prefs service release

Hi Felix, I have now updated JIRA. I was about to write an email asking one of the PMCs to upload the artifacts in the dist area. Thanks for doing the needful. Thanks, Sahoo On Monday 12 August 2013 11:14 AM, Felix Meschberger wrote: Hi Sahoo I granted you permission on JIRA. I also

[ANN] Apache Felix Preferences Service version 1.0.6 Released

The Felix team is pleased to announce the release of Apache Felix Preferences Service version 1.0.6: http://felix.apache.org/site/apache-felix-preferences-service.html This release is available from http://felix.apache.org/site/downloads.cgi and Maven: dependency

Updating obr with latest release of prefs service

Hi, The process as documented in [1] to update obr is not clear to me. How do I actually update repository.xml with released artifacts? Do I checkout from the svn tag and run the maven command? It does not sound correct, since it will lead to regeneration of artifacts. Ideally I would like

Re: Updating obr with latest release of prefs service

Hi Sahoo Good point. I am not sure, whether the package build phase would be sufficient and you don't actually need the install build phase. The actual repository.xml maintenance takes place in the org.apache.felix:maven-bundle-plugin:deploy goal which just adds references to the maven

Re: [DS/SCR] Configuration Binding

Hi Am 12.08.2013 um 08:16 schrieb Marcel Offermans: Hello Felix, On Aug 12, 2013, at 7:52 AM, Felix Meschberger fmesc...@adobe.com wrote: Currently our Declarative Services implementation statically binds configuration to the using bundle when such configuration is used to configure a

Re: [DS/SCR] Configuration Binding

Hi, I was under the impression that setting the location of the configuration to null when the bundle that owns the configuration is uninstalled was the responsibility of config admin. Config admin sets the location when you call getConfiguration using the bundle's CA, surely it is also CA's

Re: [DS/SCR] Configuration Binding

I don't think you're missing something. The spec states CA should be doing that already, so if our implementation is not, we should raise a bug. Greetings, Marcel On Aug 12, 2013, at 9:40 , David Jencks david_jen...@yahoo.com wrote: Hi, I was under the impression that setting the location

Re: [DS/SCR] Configuration Binding

See FELIX-3360, where I raised the same issue and provided a patch. The patch may be outdated by now, I didn't check recently. Regards Julian [0] https://issues.apache.org/jira/browse/FELIX-3360 On Mon, Aug 12, 2013 at 9:42 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: I don't

[jira] [Commented] (FELIX-3360) Bundle location is statically set for dynamically bound bundles

[ https://issues.apache.org/jira/browse/FELIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13737158#comment-13737158 ] David Jencks commented on FELIX-3360: - I am quite sure this is a CA problem not a DS

Re: Updating obr with latest release of prefs service

It's the maven-bundle-plugin:deploy goal that takes care of updating obr, so I would like to believe package phase would be sufficient. But, it's still not clear how I am supposed to update obr using the artifacts that are already created during release process? If I checkout from the svn tag