Geek Answers Handbook

Package OSGI project as a single jar?

I have a large OSGI package that I want to pack and publish as a single jar file. I'm trying to figure out what is best for packing several cans into one large can.

So far, the best option I've seen is a project with one bank. However, the structure we use extracts jar files from the plugins directory and one-jar seems to want / require all jar files to be stored only in the lib directory. Maybe there is an easy way around this, I did not look completely at the architecture to know, as I am still trying to decide which approach is best.

Any suggestions on other approaches to the package of multiple OSGI suites in one bank and / or how I would like to make it work in one bank are welcome.

thanks

+4
source share
3 answers

An alternative solution would be to run your packages using PojoSR instead of running them in OSGi. PojoSR in a nutshell implements the OSGi service layer without a module. One of the side effects of this is that you can easily package your application as an executable JAR file. When you run this JAR, it also does not need to create a package cache on disk.

For more information about PojoSR, go to:

+1
source

Using the Apache Felix Maven Bundle plugin, I believe that this option can accomplish what you are looking for. http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html

0
source

The Apache Sling maven-launchpad plugin generates an executable jar (and possibly a war file and a Karaf descriptor) from the list of packages, see http://sling.apache.org/site/maven-launchpad-plugin.html

The Sling installer can be used to download additional packages from the file system or from other sources, see http://sling.apache.org/site/jcr-installer-jcrjcrinstall-and-osgiinstaller.html

0
source

More articles:


All Articles