If we were to use OBR, the camel jasypt would only consis of the camel-jasypt bundle and the resolver="obr" flag on the feature. All the dependencies resolution would be done by obr which is able to look at the current platform level ans find the needed bundles.
On Tuesday, October 12, 2010, Claus Ibsen <[email protected]> wrote: > On Tue, Oct 12, 2010 at 8:01 AM, Jean-Baptiste Onofré <[email protected]> > wrote: >> Hi Claus, >> >> Up to now, AFAIK, it's not possible to define a feature with JDK specific >> bundles (the descriptor is static). You can add some JRE/JDK specific >> definition in etc/jre.properties but it's global to the kernel (not >> dedicated to a given feature). >> >> Anyway, I think it's interesting. >> >> We can extend the feature deployer to support this kind of "conditions". >> >> I'm gonna raise a Jira task around this. >> > > Thanks for the reply. > > For example the camel-jasypt feature requires a IBM bundle to work on > JDK 1.5, where as on 1.6+ it works fine without. > So would be nice to have such an option in the feature. > > A bit more extreme option could have an option for the OS. So you can > add bundles depending on the OS, for example AIX may require some > special bundle. > Well in fact its more a difference between IBM and SUN JDK. So maybe > an option for that. > Anyway that may be a bit over the top. > > >> Regards >> JB >> >> On 10/12/2010 06:16 AM, Claus Ibsen wrote: >>> >>> Hi >>> >>> I wonder if its possible in the features.xml file to define a bundle >>> being qualified depending on the current JDK? >>> >>> For example if you run JDK 1.5 you want the bundle included. If you >>> run JDK 1.6+ you do NOT. >>> The option should most likely support a range similar to the OSGi >>> versioning. >>> >>> Maybe something similar to this: >>> <bundle jdk="[1.5,1.6)">mvn:xxx/yyy/2.2</bundle> >>> >>> An example would be many of the encryption frameworks which requires >>> additional jars to run on JDK 1.5, where as 1.6 provides API and >>> chipers out of the box. >>> And we could have a similar situation when JDK 1.7 comes out. Where >>> you may need additional JARs on 1.6 and not on 1.7. >>> >>> I could not find such information at >>> http://karaf.apache.org/46-provisioning.html >>> >>> But it could be the documentation is outdated >>> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
