On Wed, May 5, 2010 at 21:47, Chris Blunck <[email protected]> wrote:
> I think that would be a very elegant solution to the issue of starting > dependencies from a feature. > > Well, in my mind, it would install dependencies, not only start them. > On another note ... is it possible to generate a feature.xml from > maven-bundle-plugin? If that's the case then perhaps maven-bundle-plugin > could embed multiple <bundle> lines that reference all of the bundles (and > all their dependencies). > > Karaf has a maven plugin which can actually create a feature descriptor. But it's kinda difficult to generate a very nice one, as you need to very tightly control your dependencies. > Just a thought... > > > -c > > On Wed, May 5, 2010 at 3:34 PM, Guillaume Nodet <[email protected]> wrote: > > > Yes, that would not work. If you want to use OBR to provision your > > applications, you can do so using the obr commands, but that's not > > currently > > supported by the features provisioning system. > > > > In any case, if we were to support such a thing, i would not use a > <bundle> > > element, as this is really supposed to identify one bundle, not a group > of > > bundle. > > > > I think we could add a flag on the feature definition that would inform > the > > features service to use OBR to download any missing dependency needed to > > resolve the list of bundles listed in the feature. I think that would > > solve your problem in a nice way. What do you think ? > > > > On Wed, May 5, 2010 at 21:28, Chris Blunck <[email protected]> wrote: > > > > > Hello- > > > > > > I'm working on provisioning my application and the use of features and > > OBR > > > seems like a very natural way to approach the problem. > > > > > > I have used the maven-bundle-plugin to create bundles for each of my > > > subprojects and I have generated an obr.xml file that describes the > > > capabilities and requirements of each bundle. > > > > > > I am working with BundleRepository v1.6.0. I "obr add-url" a path to > my > > > generated obr.xml and I am able to "obr start X". Everything works > > > swimmingly - X is started along with all of X's dependencies. > > > > > > I have also created a feature XML file that contains all of my relevant > > > configuration information as well as 1 feature: MyApp. This is the > > > definition for MyApp: > > > <feature name="MyApp" version="1.0.0"> > > > <bundle>obr:C</bundle> > > > </feature> > > > > > > C is a bundle that depends on B, and B depends on A. It's basically C > -> > > B > > > -> A (a very simple dependency graph). > > > > > > "obr start C" works. > > > > > > features:install C results in "Unresolved constraint in bundle C: > package > > > b". > > > > > > Should the feature bundle delegate to OBR in such a way that all > > > dependencies will be brought in as well? > > > > > > Or should I list ALL of my dependencies in the <feature>? > > > > > > > > > -Chris > > > > > > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > ------------------------ > > Open Source SOA > > http://fusesource.com > > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
