Hi Eric,
I just tried the following scenario:
1. With Karaf 4.2.2-SNAPSHOT freshly built, I created an instance with:
instance:create test
instance:start test
instance:connect test
2. I dropped a bundle in the test instance deploy folder.
I can see the fileinstall "trigger" in the log:
2018-12-04 21:21:43,375 | INFO | nces/test/deploy | fileinstall
| 10 - org.apache.felix.fileinstall - 3.6.4 | Started
bundle:
file:/home/jbonofre/Workspace/karaf/assemblies/apache-karaf/target/apache-karaf-4.2.2-SNAPSHOT/instances/test/deploy/commons-lang-2.6.jar
So, it looks good to me.
Regards
JB
On 02/12/2018 20:15, Eric Lilja wrote:
Hi, is it possible to consider including KARAF-5934 for 4.2.2? I saw it
was just tentatively postponed to 4.2.3.
Also, is the deploy folder enabled by default? I downloaded the binary
distribution (version 4.2.1), and created a new instance with feature
scr enabled. Everything else vanilla. I put a bundle in the deploy
folder but it doesn't get installed, no interesting output from log:tail
either, so no failures. Just like the directory was not monitored at all
(I did use the deploy directory in the instance I created).
Furthermore, output from scr:list seems to lack line breaks. This is
under Windows, with Cygwin (Mintty) as terminal. Also tried with
TakeCommand under Windows, which used to work really well with Karaf,
but when one does bundle:list -s -t 0 for example, a lot columns
contains only ?-characters (question marks). Also scr:list looks bad
under it.
- Eric L
