Agree! I think they are trying to achieve something similar with records.
I compile with intellij, and it works fine. I package the exec with maven and can get it to run in my ide without issues.
The error only occurs after I copy the same package (executable jar plus classpath libs) on a different machine, and try to run it there.
I will need to review all the different steps again. We'll see...
Wild guess... Maybe a missing "runtime" scope for one of the lombok dependencies? It may be in your build machine maven repo and isn't being bundled with the deployable?
To be honest I remember Lombok being compile time only.
Oh, from the docs "Lombok should be used at the provided scope", it's compile time only. So something funny is going on!
Very interesting, thanks for this! I'll definitely check it out tonight.
