On 26/04/13 17:08, Raymond Auge wrote:
Hello All,
(this may already exist, if so forgive the noise... and then please
point me to it :) )
Does it make any sense to have a means for bundles to declare their host
repository, and if there is such a capability installed in the
framework,
On Fri, Apr 26, 2013 at 11:14 AM, Ferry Huberts maili...@hupie.com wrote:
On 26/04/13 17:08, Raymond Auge wrote:
Hello All,
(this may already exist, if so forgive the noise... and then please
point me to it :) )
Does it make any sense to have a means for bundles to declare their
One further question, is it possible to have an optional
Require-Capability?
I'm trying to think of the semantics around being able to add a repo if
there is an repo admin service, but if there isn't, just carry on, falling
back to existing behaviour which would fail to
resolve the bundle unless
Yep...
Require-Capability: osgi.service;
filter:=(objectClass=org.example.foo.MyService); effective:=active;
resolution:=optional;
(the 'effective' directive is not directly related to optionality, but is
probably a good idea when talking about a service dependency)
Neil
On Fri, Apr 26, 2013
On 26/04/13 19:45, Ferry Huberts wrote:
On 26/04/13 19:39, Raymond Auge wrote:
On Fri, Apr 26, 2013 at 12:59 PM, Neil Bartlett njbartl...@gmail.com
mailto:njbartl...@gmail.com wrote:
Yep...
Require-Capability: osgi.service;
But isn't the R5 resolver doing just that?
In bndtools, the R5 resolver is collecting all the dependencies and
creating a complete runtime, and effectively pulling from a pre-configured
list of repositories.
All this is doing is adding into that mix a mechanism to enable resolution
of
Well don't get me wrong... it's a potentially valuable idea to include that
kind of information in the manifest, if even it takes a while for us to
figure out the best way to use it.
For example, who or what is the component responsible for installing this
bundle in the first place? If it's
