tag:blogger.com,1999:blog-8119361957970651148.post7091478628916652239..comments2023-07-26T05:57:13.007-02:30Comments on I code by the sea.: Making OSGi deployments easier with feature filesicbtshttp://www.blogger.com/profile/04070633252162860464noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8119361957970651148.post-8557587399390693042014-12-24T02:51:24.918-03:302014-12-24T02:51:24.918-03:30Hi,
Thanks for your post!
I am looking for tips ...Hi,<br /><br />Thanks for your post!<br /><br />I am looking for tips to getting the karaf files deployed via a Jenkins Build system. I am quite new to karaf and trying to figure the most decent and right way to deploy this. <br /><br />What would be the best way to deploy this into the osgi container? Deploy would include updating the older version with new available version. restarting service for all property changes. Any scripts that would suite this type of deployment? <br /><br />Thanks,<br />SubbuAnonymoushttps://www.blogger.com/profile/07759148754524406806noreply@blogger.comtag:blogger.com,1999:blog-8119361957970651148.post-42538465038272446942014-04-30T07:01:09.651-02:302014-04-30T07:01:09.651-02:30Awesome, simple explanationAwesome, simple explanationAnonymoushttps://www.blogger.com/profile/14127595540104408084noreply@blogger.comtag:blogger.com,1999:blog-8119361957970651148.post-7973046736582297242012-03-28T21:30:39.059-02:302012-03-28T21:30:39.059-02:30Hi Jimmi,
Thanks for your post!
As to your comm...Hi Jimmi, <br /><br />Thanks for your post!<br /><br />As to your comments regarding issues using features files in production (upgrades, uninstalls, etc), a lot of these issues lead to the development of Apache Karaf Kars.<br /><br />An Apache Karaf KAR (KARaf archive) is a zip file which gathers a features XML and all bundles and configuration files dependencies. It means that a KAR is an atomic artifact which can be deployed without an Internet connection (as all is shipped in the KAR file itself). This leads to a some what easier administrative process for provisioning an application.<br /><br />For more information on Apache Karaf Kars please see my previous post A brief introduction to Apache Karaf Archives (kars).<br /><br />-Jamieicbtshttps://www.blogger.com/profile/04070633252162860464noreply@blogger.comtag:blogger.com,1999:blog-8119361957970651148.post-90209830452402999762012-03-28T07:02:14.072-02:302012-03-28T07:02:14.072-02:30Hi Jamie,
Great post - thanks for this.
You can ...Hi Jamie,<br /><br />Great post - thanks for this.<br /><br />You can also use features files for creating Karaf distributions - e.g. for repeatable installations across multiple servers when you don't want bundles downloaded from Maven repos at runtime. <br /><br />I've also found it useful to attach the features XML as an artifact to the Maven build using the build-helper-maven-plugin (http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html). That way it gets deployed to a Maven repo & the actual feature file (using classifier of feature & type of xml) can be used as a dependency, perhaps of other features projects. That way you can chain features files to produce even better flexibility around your deployments.<br /><br />A couple of problems I do have with using features though is that uninstalling features doesn't work particularly well. What if a bundle is required by multiple features, or installed manually rather than through a features installation? Should the bundle be uninstalled in these cases if a feature requiring it is uninstalled? Also there is no facility to upgrade features (i.e. upgrading versions of bundles in those features). Adding this functionality would make it more complex, like a full package manager like APT, & adding that complexity may not be desirable. Any thoughts on that?<br /><br />Thanks,<br />JimmiAnonymoushttps://www.blogger.com/profile/16558184867995788157noreply@blogger.com