Consider using Java requireNonNull instead of Guava checkNotNull in generated code

[gaul]

checkNotNull triggers Modernizer violations in generated code: gaul/modernizer-maven-plugin#28. Immutables already requires Java 7 so generated code can use requireNonNull.

[elucash]

Thank you for reporting the issue!
Immutables able to generate JDK only code, including mentioned requireNonNull. In order to do this either of the following should be true:

• There is no Guava on the class-path
• Or style set to force jdk only mode: @Value.Style(jdkOnly = true, ...). (see guide on how to apply styles)

Please check if you can apply any of the above.
If there need to mostly use Guava in generated code as it is, but to have requireNonNull or other goodies to replace guava's ones, then we could discuss complete set of API or other workarounds.

[gaul]

@talios Does using JDK-only code address your issue?

[talios]

@andrewgaul Just noticed this - is that a new setting or has it been there for awhile? Seems to work a treat cheers!

[elucash]

it's one of the main new features in 2.0: Guava is no longer a required dependency, albeit still fully supported if present. jdkOnly setting is to force usage of JDK only utilities as classpath may just contain Guava even if you don't want to use it in a generated code (and still if you use explicit ImmutableList from guava, for example, it should work as expected).