Quoting Paul Merlin <[email protected]>:
Quoting Rickard Öberg <[email protected]>:
Hi,
So far we used tried to mainly use the JDK logging in Qi4j. However, in
my own projects I'm going with SLF4J, and most of the libraries I use
seem to be using that as well. One tiny detail I like about it is that
it has .debug() methods, which the JDK doesn't. It is also quite easy to
replace the backing log library, with either the JDK or log4j (which I
use).
So, therefore I would like to suggest that we switch from the JDK to
SLF4J in Qi4j. I would also suggest that Qi4j Core, the runtime
specifically, start doing more debug output. That would make it easier
to track what's going on both in development and production.
WDYT?
regards, Rickard
I personnaly use SLF4J in every project I work on. Having Qi4j use
it too would
be really nice from development & exploitation point of view.
Here is my +1
Yep, I agree. I'll change all of my Qi4j-related projects to SLF4J,
since I've accidently used java.util.Logging class in some places.
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
