@Target(value=TYPE) @Retention(value=RUNTIME) public @interface HandlerPriority
@Value can cause the class to be marked final, and this affects the behaviour of @EqualsAndHashCode. By ensuring that
the handler for @Value always runs before the handler for @EqualsAndHashCode, the code is simpler: The @EqualsAndHashCode handler
does not have to check for the presence of a @Value annotation to determine whether to generate the canEqual method or not.
A new priority level can also be used to force a reset of the resolved model, i.e. to add generated methods to the symbol tables. Each platform implementation (javac, ecj, etc) may have additional marker annotations required to indicate the need for the reset.
| Modifier and Type | Required Element and Description |
|---|---|
int |
value |
| Modifier and Type | Optional Element and Description |
|---|---|
int |
subValue
This can be used to differentiate 2 handlers with the same value to be at a different handler priority anyway.
|
Copyright © 2009-2013 The Project Lombok Authors, licensed under the MIT licence.