System.out.println instead of slf4j about jacop HOT 2 CLOSED

Thank you raising an issue. Sorry for late answering ;).

Logging in Java is messy. We tried to reduce the amount of depedencies in JaCoP to have the least amount of impact on developers using JaCoP. This is a reason why we do not have it.

I agree that slf4j is a good framework, so if I was adding logging I would add this. I tried using AspectJ to weave in logging statements but then something bizzarre happened - even if logging was inactive it caused some serious slow down of JaCoP. Possibly, some JIT/JVM optimizations were not being triggerred.

I will put those printouts in DepthFirstSearch within an if statement based on existing printInfo boolean variable.

Was there another class that was printing info through System.out.println without the possibility to switch it off?

from jacop.

I checked DepthFirstSearch.java in JaCoP 4.4.0 and all System.out.println are within if statements based on printInfo boolean variable so it is possible to switch it off.

Please let me know if you have any other System.out.println statements that were not possible to switch off.

from jacop.