Jenkins 2.43 introduced a change to display stack traces in a "logical" order.

The standard order for displaying stack traces shows the "least important" information at the top. For an end-user (ie, not a Jenkins administrator / developer / java export) this is generally more useful, as it provides (in theory) a summary of the error, rather than the low level technical details.

While this change may make sense for developers, it does not make sense for all Jenkins users. Additionally, most Java developers (for whom this is in theory most useful) are used to the standard way stacktraces are presented.