Thank you a ton for the hint Niels and Ceki
I've added support to LocationAwareLogger and now slf4j-fluent logs the
correct calling class name info
I've just deployed the new version, 0.9.0, which will be available on
maven central as soon as they sync their servers
cheers
federico
niels
See LoggerContext.getFrameworkPackages() method.
Sample use:
ContextUtil contextUtil = new ContextUtil(context);
contextUtil.addGroovyPackages(lc.getFrameworkPackages());
On 15.02.2019 23:27, Ceki wrote:
Hi Federico,
The list of packages serving as frontiers in location computation
Hi Federico,
The list of packages serving as frontiers in location computations can
be adjusted quite easily. It's a non problem.
--
Ceki Gülcü
On 13.02.2019 18:18, Federico Fissore wrote:
niels ha scritto il 13/02/19 alle 13:54:
Have in mint to set the FQDN in a correct way. I would guess t
See the message from Ceki
"
Hello Niels,
I am following up on our discussion on stackoverflow.
Since logback-classic exposes its API via SLF4J, you would probably
want to extend org.slf4j.Logger. See the org.slf4j.ext package for
extension examples. The org.slf4j.ext.LoggerWrapper [1] class shoul
Am 13.02.19 um 18:18 schrieb Federico Fissore:
One solution is to change package of slf4j-fluent from
"org.fissore.slf4j" to "org.slf4j", but it seems politically incorrect
It's not just "politically incorrect". The JVM ecosystem is moving
towards disallowing classes from different jars in the
niels ha scritto il 13/02/19 alle 13:54:
Have in mint to set the FQDN in a correct way. I would guess that with
your implementation the %C and %M of log4j will fail.
True, it's a known issue. I don't have a fix at the moment.
Implementations such as logback and log4j filter out *their* classe
Have in mint to set the FQDN in a correct way. I would guess that with your
implementation the %C and %M of log4j will fail.
Am Fr., 18. Jan. 2019 um 16:07 Uhr schrieb Federico Fissore <
feder...@fissore.org>:
> Hi everyone
>
> Just a quick announcement: slf4j-fluent 0.6.0 has been released and i
Hi everyone
Just a quick announcement: slf4j-fluent 0.6.0 has been released and it
features two more APIs
every(int): logs the same entry only every `int` times
every(long, ChronoUnit): logs the same entry for example every 2
seconds, or 100 millis...
slf4j-fluent is meant to be a port of F
Matt Sicker ha scritto il 09/01/19 alle 17:26:
On Wed, 9 Jan 2019 at 06:05, Federico Fissore wrote:
...
its cost is not zero, as it creates a new object instance every time
error/info/xxx methods are called, ...
Wouldn't escape analysis eventually cause inlining anyways? Garbage
may not be to
On Wed, 9 Jan 2019 at 06:05, Federico Fissore wrote:
> ...
> its cost is not zero, as it creates a new object instance every time
> error/info/xxx methods are called, ...
Wouldn't escape analysis eventually cause inlining anyways? Garbage
may not be too big an issue there, especially since you've
Hi everyone
I've started coding a fluent API for slf4j, slf4j-fluent, which is
available on github [0]
I started coding it after seeing Flogger [1]: I've found its API nice to
read but I didn't want to change my code in order to use a different
logging framework
slf4j-fluent is just syntac
11 matches
Mail list logo
