Am 02.12.2015 um 15:51 schrieb Guillaume Nodet:
Remember resource repositories can also point to other resource
repositories.
Interesting. I did not know this. That makes it a lot easier of course.
I read in the bndtools doc that it support multiple kind of
repositories. Can't we just add support for feature repositories ?
It could work. Would we simply add all the bundles in the feature
repository as an index?
I think one issue might be that a feature repository does not contain
the OSGi metadata. So we would need to
create it on the fly and probably cache it.
One other approach would be a maven plugin to create an OBR index from a
feature repository. So the result would directly work in bndtools.
Probably this would be the simplest way to bring a lot of the karaf
features into bndtools for development.
For short term it could help to be able to use existing feature
repositories. For long term I really like the idea to back feature
repositories with an index.
It makes the individual features and the whole feature creation process
a lot simpler. So probably it makes sense to follow both paths.
What we would need is the input that was given to the bndtooling
during resolution / validation.
If we have this, we could certainly have a successful resolution too.
Tough having a list of bundles, i.e. the output of the resolution
would work too.
Yes I think both approaches could have their place.
For the application mode the fully resolved list of bundles could be
great. We could then even start a karaf without the feature service and
use startup.properties to list the bundles.
Another approach would be to create a feature from the resolved bundle
list.
In both cases a problem is that karaf already starts with some bundles.
So for the first approach we would need to somehow add these bundles
either already in bndtools or later.
For the second approach we would probably want to remove the initial
bundles from the feature. Maybe they could also just stay there .. not
sure though.
Christian
