https://projectlombok.org: Spice up your java: Automatic Resource Management, automatic generation of getters, setters, equals, hashCode and toString, and more! 
/*
 * Copyright (C) 2012 The Project Lombok Authors.
 * 
 * Permission is hereby granted, free of charge, to any person obtaining a copy
 * of this software and associated documentation files (the "Software"), to deal
 * in the Software without restriction, including without limitation the rights
 * to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 * copies of the Software, and to permit persons to whom the Software is
 * furnished to do so, subject to the following conditions:
 * 
 * The above copyright notice and this permission notice shall be included in
 * all copies or substantial portions of the Software.
 * 
 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
 * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
 * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
 * THE SOFTWARE.
 */
package lombok.core;

import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;


Used to order the way handlers are run. Handlers with a lower priority value are run before handlers with higher priority values. For example, @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.

/**
 * Used to order the way handlers are run. Handlers with a lower priority value are run before handlers with higher priority values.
 * For example, {@code @Value} can cause the class to be marked final, and this affects the behaviour of {@code @EqualsAndHashCode}. By ensuring that
 * the handler for {@code @Value} always runs before the handler for {@code @EqualsAndHashCode}, the code is simpler: The {@code @EqualsAndHashCode} handler
 * does not have to check for the presence of a {@code @Value} annotation to determine whether to generate the {@code canEqual} method or not.
 * <p>
 * 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.
 */
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.RUNTIME)
public @interface HandlerPriority {
	int value();
	
	
This can be used to differentiate 2 handlers with the same value to be at a different handler priority anyway.
DO NOT USE THIS unless someone has been crowding out the numbers and there's no room left.

/**
	 * This can be used to differentiate 2 handlers with the same value to be at a different handler priority anyway.
	 * <strong>DO NOT USE THIS</strong> unless someone has been crowding out the numbers and there's no room left.
	 */
	int subValue() default 0;
}