Thanks for helping address this.

For anyone on Lucee 5.3.5, you can merge these CFConfig settings into your .cfconfig.json file to get the old behavior back:

Or set them manually like so:

best use SystemOutput if you need to write to console, System.out|err not necessary writes to the console anyway, as you can see in the doc

https://docs.oracle.com/javase/7/docs/api/java/lang/System.html#err

changed default target to system

you cannot expect system.out to end in the console.

But that's not really an ok change. java.lang.System.out.println should write to the console output of a server. That's the standard for every Java app that's ever existed. Why does this change need to be made? I understand if you want to redirect Lucee's logging elsewhere, lucee can put its logs where it wants (though I would point out that console logging IS the standard for docker/container deployments, so I'd stick with it) but for my application code, a java-based app should be able to write to the console using the system.out print buffer. That should not have changed.

As it stands LogBox's ConsoleAppender is now completely broken on Lucee 5.3.5 Also, let me remind you that messages sent to the out buffer are not sent to a log file at all. From what I can tell, they go nowhere! (I have checked all the log files) That isn't really an acceptable

use the function system output instead.

I addressed why that is not a valid workaround in the ticket description.

this is expected see

before that setting did not work as it should, now it does. you cannot expect system.out to end in the console. use the function system output instead.