This issue is now more than 3 months old, and I've been holding off on upgrading the lombok-maven-plugin as a result because this broke my unit test. By the 👍 from @rspilker, I'm left to believe that this is a legitimate issue, but there seems to be no traction on resolving it.

Will this be resolved?

I think setting the source version never worked like this for delombok. It does not use the normal compilation, it starts its own compiler task and only pass a subset of compiler flags. Unfortunately there is no way to set the compiler version at the moment.

A normal compilation and lombok tests work as expected.

I don't really see what we can meaningfully look at. Perhaps the version of the java runtime that delombok is running on top of, but that's merely a pretty good guess, not a surefire thing - perhaps a decent default, but it needs a setting even then.

It also doesn't feel like a formatting option (java -jar lombok.jar delombok --format-help).

Perhaps delombok should gain a --source option; perhaps in the future we'll make more features change what they generate based on the language features available.

We already have parameters for some compiler arguments, how do we decide which one will be added as delombok parameter?

@awhitford
Delombok stores the Context, you can use reflection to edit it and inject the source version.

Class<?> contextClass = Class.forName("com.sun.tools.javac.util.Context");
Field contextField = delombokClass.getDeclaredField("context");
contextField.setAccessible(true);
Object context = contextField.get(this.delombokInstance);

Class<?> optionsClass = Class.forName("com.sun.tools.javac.util.Options");
Method optionsInstance = optionsClass.getDeclaredMethod("instance", contextClass);
Object options = optionsInstance.invoke(null, context);

Method optionsPut = optionsClass.getDeclaredMethod("put", String.class, String.class);
optionsPut.invoke(options, "-source", "1.6");