pnoltes opened a new issue, #714: URL: https://github.com/apache/celix/issues/714
# Intro Currently, it is difficult to install a generated Apache Celix container executable, including its required bundles and an optional config.properties file. This challenge can prevent users from using Apache Celix to create installable applications. # Bndtools bndrun export Bndtools, a tool for Java OSGi build and development, has support for creating a single JAR that contains an OSGi framework, bundles, and configuration. > Bndtools can export a bndrun file to an executable JAR. This is a JAR that can be executed in any Java VM. The JAR contains the framework and all required bundles. When it runs with the venerable java -jar x.jar command it will unpack itself and launch a framework. The continuous integration can build this executable JAR. # Self-Contained Apache Celix Executable Create a solution that allows users to create an Apache Celix container that is installable and runnable from a single executable file. The executable or extracted Apache Celix container can have normal libraries dependencies (i.e. libcurl, libcelix_framework, etc), but should not depend on external bundle zip files or a config.properties file. A possible solution could be [Makeself](https://makeself.io/). Note that makeself is GPL, but mentions the following: > Makeself itself is covered by the [GNU General Public License](http://www.gnu.org/copyleft/gpl.html) (GPL) version 2 and above. Archives generated by Makeself don’t have to be placed under this license (although I encourage it ;-)), since the archive itself is merely data for Makeself. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@celix.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
