Messages leaking to console out

https://github.com/lucee/Lucee/commit/86a497210e92d7523389fe081a0f2b71e973353a

Your point on the cases when you want it is valid. The question might be better put is there a way to trap it and prevent it until you do want it. Many tools that have different levels of output. In this case it would be awesome if the default were to be far less verbose.

problem is that the core loads all the log4j stuff, so the loader has not access to log4j on startup when the core is not loaded yet.

only pointing out possibilities. sometime you wanna have everything written to console in a file, because you don't have access to console, as btw Tomcat does as well.

Hi, can you explain how or why I would use those settings? What would I change them to? To be clear, the issue this ticket is presenting is not that I want to change or remove the system out or error. In fact, I very much want to preserve the system out in Lucee so CommandBox can work. What I need to happen is for the improper logging that Lucee is sending straight to the system out needs to instead be routed through log4j or another suitable logging library so it can be handled appropriately. These "quick and dirty" logging lines that are sending content directly to system out from inside Lucee is the problem as that gets leaked out to any console app trying to use Lucee. I need to be able to control what gets sent to the out stream myself.