rwoolf <r...@rosswoolf.com> writes: > My blueprint xml file is my "bundle." I drop the blueprint xml file into > the deploy directory. I have two different blueprint xml files for the two > different contexts. So in this regard they are different bundles. But > they are not packaged as jar based bundles. I'm guessing from what you > said that neither blueprint or camel will be able to provide any means to > declare a specific version dependency. I would need to package these > blueprint xml files into real jar bundles in order to be able to declare > version dependencies. Am I right? > > It would be really nice if I could declare a version dependency in the > blueprint xml file and then just deploy that xml file. Since blueprint is > geared towards OSGi it would be great if I could do something like this. >
The version imports are going to be a function of the osgi deployment, and in this specific case would be driven by the Karaf "Blueprint Deployer" see [1], specifically the section on customizing the generated manifest where it shows <manifest xmlns="http://karaf.apache.org/xmlns/deployer/blueprint/v1.0.0";> Require-Bundle= my-bundle </manifest> The Require-Bundle header is documented at osgi.org at [2]. [1] https://karaf.apache.org/manual/latest/users-guide/deployers.html [2] http://wiki.osgi.org/wiki/Require-Bundle Hope that helps. -John
