Hi Eric,
The update to maven-bundle-plugin 4.1.0 introduces some other changes
(as the requirements/capabilities created are extended). Why do you need
this for 4.2.2 ? It's transparent for you as user.
So I will try but without strong commitment. Reasonably, I would prefer
to target in 4.2.3 as I'm planning 4.2.2 for this week. So, it will be a
best effort.
Yes, deploy folder is enabled by default. Did you deploy a bundle or a
raw jar ?
The line breaks should be fixed already (you can test on 4.2.2-SNAPSHOT).
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
