Agree about the optional, but it could head to a refresh, so I would
like to check.

I keep you posted.

Regards
JB

On 04/10/2019 11:38, J. Brebec wrote:
> Pax Logging using Knopflerfish is not new, however the jar is required only 
> since v1.11 of pax logging (it has been introduced in PAXLOGGING-252). The 
> jar is not needed at runtime, because it's embedded into pax-logging.
> 
> In my opinion, the dependency should be marked as optional in the pom of 
> pax-logging-service. Having a required dependency present only in a private 
> maven repository cn be easily a bad experience for people like me behind a 
> corporate proxy.
> 
> Do you know how to get ride of the println of the wrapper bundle ? This 
> bundle is started before pax-logging and the default logger use 
> System.println. It happens in custom distribution or when using the static 
> framework.
> 
> Regards,
> Jérémie 
> 
> On 2019/10/04 08:23:28, Jean-Baptiste Onofré <[email protected]> wrote: 
>> Hi,
>>
>> knoperfish dependency is in pax-logging-api and it's not new.
>>
>> The karaf-docker-example creates a distribution without problem because
>> I have the artifacts on my repo.
>>
>> The knopflerfish artifacts are not on Central anymore but on repo:
>>
>> https://www.knopflerfish.org/releases/5.0.0/maven2/
>>
>> If you add an exclusion in pom dependency it should work.
>>
>> I have two proposals here:
>>
>> 1. remove the dependency in pax-logging (but it could impact some users)
>> 2. add the bundle as "installed" to populate karaf system folder and not
>> go on remote repositories.
>>
>> Regards
>> JB
>>
>> On 04/10/2019 10:03, J. Brebec wrote:
>>> Do you remember the name of the property or where I should look ? I didn't 
>>> see anything on this suject in the release note of pax logging.
>>>
>>> Thanks
>>>
>>> On 2019/10/03 18:01:24, Benjamin Graf <[email protected]> wrote: 
>>>> If I remember right there is a new option to be set since pax-logging 1.11.
>>>>
>>>> Might not be set yet in Karaf 4.2.7
>>>>
>>>> Regards
>>>> Benjamin 
>>>>
>>>> Am 3. Oktober 2019 13:59:01 MESZ schrieb "J. Brebec" 
>>>> <[email protected]>:
>>>>> Thanks.
>>>>>
>>>>> It's probably related to the upgrade to pax-logging too, but when I
>>>>> launch Karaf 4.2.7 (on windows), there is a System.println visibile in
>>>>> the console :
>>>>>
>>>>> org.ops4j.pax.url.wrap
>>>>> [org.ops4j.pax.url.commons.handler.HandlerActivator] DEBUG : Handler
>>>>> for protocols [wrap] started
>>>>>
>>>>>
>>>>> On 2019/10/03 09:10:43, jbonofre <[email protected]> wrote: 
>>>>>> Let me take a look. It's probably a side effect of pax-logging 1.11
>>>>> update.
>>>>>>
>>>>>> I keep you posted.
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
>>>>>>
>>>>
>>>> -- 
>>>> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
>>
>> -- 
>> Jean-Baptiste Onofré
>> [email protected]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>

-- 
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com

Reply via email to