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 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 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* classes
when looking for the value of %C, and of course slf4j-fluent is not
*their* stuff so it's considered the logging class
One solution is to change package of slf4j-fluent from
"org.fissore.slf4j" to "org.slf4j", but it seems politically incorrect
What do you think?
federico
--
--
Ceki Gülcü
_______________________________________________
slf4j-user mailing list
slf4j-user@qos.ch
http://mailman.qos.ch/mailman/listinfo/slf4j-user
