See apache/logging-log4j2#3125 for context, thank you very much for your consideration. I understand snapshot builds are not preferable but given the severity of this issue there is a good rational for using it temporarily.

The only downside are the warnings for which another issue at log4j has already been opened. They are purely warnings and can be ignored as confirmed by their developers.

@4drian3d can this be looked at and pulled? I noticed the thumbs down but this is a serious issue in any plugin using javascript placeholders

I'm not really fond of harming build stability to jump back towards a snapshot to mitigate an issue in a 3rd party library which has nothing to do with us which have already mitigated the issue in their own snapshots

the annotation processor group ID also looks look wrong, but I'm not really in a place of reading up on Graal/log4js stuff to figure this out. Ideally, we'd just disable their graal VM metadata generation if viable as we don't even support native image, so, it shouldn't even matter.

@electronicboy Makes sense. So we're going to wait until the next log4j stable?