Hello JB, It sounds good. How is the jar been run, will it unpack,dynamically? Is there provisions for config template or a mechanism for a container install?
Gruss Bernd -- http://bernd.eckenfels.net ________________________________ Von: Jean-Baptiste Onofre <j...@nanthrax.net> Gesendet: Monday, June 14, 2021 7:24:10 AM An: dev@karaf.apache.org <dev@karaf.apache.org> Betreff: [PROPOSAL] features.deployer=[true|false] and new tool waiting Karaf 5 Hi guys, Following the discussion on a previous mailing list thread, I moved forward on the features resolver. I will submit a PR containing a new features.deployer=[true|false] property in etc/org.apache.karaf.features.cfg. If true, it’s the current behavior, nothing change (it’s the default). If false, we won’t use a full resolver, but a very simple one, just executing/installing what’s in the features xml/json. On the other hand, waiting Karaf 5, I would like to propose a new tool (runnable/cli/maven) to "wrap" karaf distribution and user artifacts in a ready to run jar. So, basically, it’s mean that we will be able to do something like: $ karaf-packager —version 4.3.2 —features-repos mvn:…,file:… —features foo, bar —name mystuff And the result will be mystuff.jar able to do java -jar mystuff.jar Of course, we will be able to include Karaf-packager in CI. Thoughts ? Karaf 5 already works this way and we did good progress on K5, I will share details pretty soon. Regards JB
