Hi, The best option is probably to use directly features instead of kar.
For kar, you can use the deploy folder or directly the kar service. So, IMHO: 1. You app should provide a features repo XML and upload artifacts on a repo 2. You can create a custom karaf distro including your features repo Regards JB On Thu, May 11, 2023 at 4:10 AM jose.garnica.lomeli <jose.garnica.lom...@protonmail.com> wrote: > > I have a git project that generate a kar file using jenkins pipelines, when > we deploy the kar file we need move it manually into the deploy folder of our > karaf application(the karaf application use accurev instead git) > > In your opinion, what is the best way to improve the process? > > I have some ideas > > 1- move the existing code of kar project into the same repository of the > karaf application as a maven module > > 2- inject the kar file as a maven dependecy > > I think the last one is better but I getting some issues pulling the > artifactory from our nexus repository > > So besides the options already mentioned, is there another alternative? > > My goal is avoid to deploy/install the kar file manually into my karaf > application. > > > Sent from Proton Mail mobile > >