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 a
[
https://issues.apache.org/jira/browse/FELIX-3360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737158#comment-13737158
]
David Jencks commented on FELIX-3360:
-
I am quite sure this is a CA problem not a DS p
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
wrote:
> I don't think you're missing something.
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 wrote:
> Hi,
>
> I was under the impression that setting the location of the configuration
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 r
Hi
Am 12.08.2013 um 08:16 schrieb Marcel Offermans:
> Hello Felix,
>
> On Aug 12, 2013, at 7:52 AM, Felix Meschberger wrote:
>
>> Currently our Declarative Services implementation statically binds
>> configuration to the using bundle when such configuration is used to
>> configure a componen
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 r
