Now that CommandBox is on Lucee 5, I'm seeing a few lines that are leaking to the console out that didn't used to be there in Lucee 4. I'm not even sure if these are coming from Lucee itself at all, but I'd like some pointers in squashing them
The first one is when the CLI first comes up, I often times see these lines:
Now that I'm using JSR-223, the first time I fire up a given CommandBox home, I get a TON of output to the terminal like this:
JSR-223 also includes this output on every startup:
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.
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.
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.
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.