Lombok: allow @Value to not create final classes

[rmannibucau]

Hi

when using a framework the final constraint can be quite intrusive so having a

@Value(useFinal=false)

would be very welcomed

[rschmitt]

It is impossible to guarantee that a non-final class is actually immutable, which is the whole point of @Value. Why not just use @Data?

[rmannibucau]

@rschmitt agree, even the exact reason why @Value fails when used with such frameworks. Goal is mainly to not expose setters at all. @Data(readOnly=true) would work also but sounds better on @Value IMHO. Idea being to avoid to add yet another annotation (@Setter) on all "value" objects.

[jmax01]

@NonFinal is already available.

[rspilker]

Correct

[rspilker]

As documented on the @Value page adding @NonFinal on the type gives you the desired behavior.

[tobq]

@rspilker does tht make the fields nonfinal too?

[jmax01]

@rspilker does that make the fields nonfinal too?

It does not. Fields stay final.