Hi, I did several test and it works fine for me.
Here’s the very simplest test: - Starting from Karaf 4.3.3 vanilla - I put commons-lang-2.6.jar in the deploy folder (while Karaf is stopped) - then, I’m starting Karaf with bin/karaf - When I checked the bundle:list: 54 │ Active │ 10 │ 2.6.7 │ OPS4J Pax Url - wrap: 55 │ Active │ 80 │ 2.6 │ Commons Lang So, you can see commons-lang installed and active, meaning the deployers deployed it from the deploy folder. It works for me. Can you elaborate a bit your test case ? Is it a custom distribution ? Regards JB > Le 20 sept. 2021 à 08:29, Paul Fraser <[email protected]> a écrit : > > Hi JB, > > Any result on this check? > > Paul Fraser > > On 17/9/21 9:55 pm, JB Onofré wrote: >> I checked etc I will check deploy now. >> >> Regards >> JB >> >>> Le 17 sept. 2021 à 12:29, Paul Fraser <[email protected]> a écrit : >>> >>> Hi JB, >>> >>> In my case the problem occurs using the deploy folder. >>> >>> Exact same code in 4.3.2 works, 4.3.3 does not install the deploy folder >>> files. >>> >>> Paul >>> >>>> On 17/9/21 7:04 pm, Jean-Baptiste Onofré wrote: >>>> Hi, >>>> >>>> did you updated the etc location in etc/config.properties (in the >>>> felix.fileinstall.dir property) ? >>>> >>>> I just tried and it works fine for me. Here's my test case: >>>> >>>> 1. I created etc/my.config.cfg containing foo=bar >>>> 2. I'm starting karaf >>>> 3. I can see the config loaded: >>>> >>>> karaf@root()> config:list "(service.pid=my.config)" >>>> >>>> >>>> >>>> >>>> ---------------------------------------------------------------- >>>> Pid: my.config >>>> BundleLocation: ? >>>> Properties: >>>> felix.fileinstall.filename = >>>> file:/home/jbonofre/Workspace/karaf/assemblies/apache-karaf/target/apache-karaf-4.3.4-SNAPSHOT/etc/my.config.cfg >>>> foo = bar >>>> service.pid = my.config >>>> >>>> Can you share your test case ? >>>> >>>> Regards >>>> JB >>>> >>>> >>>> >>>>> On 16/09/2021 14:31, Matthias Leinweber wrote: >>>>> Hello, >>>>> >>>>> I am having a strange issue after I updated my assembly to 4.3.3. I am >>>>> using a custom file installer location which I deploy with a feature. >>>>> >>>>> The strange thing is that the folder is not processed automatically at >>>>> startup, but if I touch a single file in the folder all others files get >>>>> processed as well. >>>>> >>>>> Any ideas? >>>>> >>>>> br, >>>>> Matthias
