Use SLF4J for logging.
Translates state machine into a target programming language.
Brought to you by:
cwrapp
Menu
▾
▴
#101 Use SLF4J for logging.
Hello,
This is an idea for a feature: logging through SFL4J (https://www.slf4j.org/) instead of sysout/syserr. This is the standard logging facade that many open source libraries rely onto and would enable to debug the programm in non-trivial use case. For example, I run my app somewhere I don't have access to syserr/sysout and rely on a real logger. When I need to debug machine specific problems, I'm stuck.
As a bonus, you could remove the ctx.setDebugFlag methods and rely on the logger's configuration.
By the way, is there any plan to use and deploy smc to Maven central ? I may help if there is any interest doing so.
I agree with this idea for the statemap.jar code. But instead of SLF4J, I suggest that java.util.logging be used since that come is part of the JVM and can be integrated with SLF4J. My reason is that I do not want developers to be forced into using a 3rd party API in order to use SMC.
You're totally right: java.util.logging (JUL) should be enough and I understand the need to avoid 3rd party dependencies.