I got the exception below with 5.4.0-SNAPSHOT today at 6:00 PM GMT+1. I suppose it also affects 5.4.0.CR1; I will attempt to reproduce and provide a fix tomorrow.
The problem was in byte-buddy. Reported and submitted a fix there: https://github.com/raphw/byte-buddy/pull/569/files
We will need to upgrade bytebuddy in order to fix the problem. Expecting a byte-buddy release early next week, see https://github.com/raphw/byte-buddy/pull/569#issuecomment-440997604
Fixed in 5.3 branch as well.