On 31/01/14 11:38, David Bosschaert wrote:
On 31 January 2014 10:28, Ferry Huberts <[email protected]> wrote:
So you're going to provide an R5 index, derived from OBR?
If you're talking about an R5-compliant xml, no I wasn't planning on
providing that, but I am planning to extend the Felix OBR runtime so
that its able to read it. I think to provide the R5-compliant
So you're going to provide an OBR index derived from an R5 index?
Seems kind of pointless to me, since the OBR format is considered
'deprecated'.
repository.xml people will probably want to use
https://github.com/osgi/bindex
That repo is kind of at a stand-still.
Nowadays bindex is developed at https://github.com/bndtools/bindex
I think that will ultimately not work out, since the R5 format is way more
expressive than the OBR format.
I'd just provide an R5 index directly from the artefacts
You are correct that the R5 xml is more expressive than the OBR XML.
So to support reading that the internal OBR representation will
probably need to be expanded a bit. I'd rather have one runtime entity
though, that supports both the Felix-OBR way of accessing it as well
as the OSGi R5 Repository Service API, rather than creating two
separate ones, TBH.
But I've only looked at this for a few days now, so I might have to
change approach if I hit a roadblock...
Cheers,
David
--
Ferry Huberts
