From 5fcb9284c13e58750ec6c36a1eae5869a5a52925 Mon Sep 17 00:00:00 2001 From: Reinier Zwitserloot Date: Tue, 29 Apr 2014 22:00:30 +0200 Subject: added docs for the new onParam feature on EqualsAndHashCode, and some tiny stylistic nitpicking. --- website/features/EqualsAndHashCode.html | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) (limited to 'website/features/EqualsAndHashCode.html') diff --git a/website/features/EqualsAndHashCode.html b/website/features/EqualsAndHashCode.html index 6b2507c6..285a27af 100644 --- a/website/features/EqualsAndHashCode.html +++ b/website/features/EqualsAndHashCode.html @@ -38,7 +38,9 @@ why such a method is necessary are explained in this paper: How to Write an Equality Method in Java. If all classes in a hierarchy are a mix of scala case classes and classes with lombok-generated equals methods, all equality will 'just work'. If you need to write your own equals methods, you should always override canEqual if you change equals and hashCode. -

+

+ NEW in Lombok 1.14.0: To put annotations on the other parameter of the equals (and, if relevant, canEqual) method, you can use onParam=@__({@AnnotationsHere}). Be careful though! This is an experimental feature. For more details see the documentation on the onX feature. +

-- cgit