Lombok's headaches are because they are touching Java compiler internals to accomplish their magic. This won't fix that.

Lombok wouldn't be nearly as troubled if it was just doing simple bytecode manipulation.

If lombok wants to stop the pain, then they'll need to stop reaching into internal APIs. They'll possibly need to remove a few features (like some of the `private final` work they are doing).

In other words, you can expect lombok to be a headache for years to come. (Maybe consider not using it? That'd be swell. Speaking as someone that curses lombok everytime jdk updates roll around.)