I'm embedding Orient into my application so I can use a plocal connection
and OLogManager is using the root logger. It looks like the best way to
solve my problem is to use 2.2.29 since the changes that are causing such
painful problems is introduced in 2.2.30.
Why is the OLogManager hard
It looks like some changes were done by laa on Nov 3, 2017 and my logging
is really hard to read because of it. Changes in OLogManager#log make it
look like Orient high jacks my logger. Is there something I can do to get
it back?
On Tuesday, February 6, 2018 at 5:15:52 PM UTC-5, Erik T wrote:
