Recipe: replace object.equals with Objects.equals

Using object.equals can lead to NPE. For example :

String a = null;
String b = "";

boolean equal = a.equals(b); // NPE

Objects.equals does not have this problem :

String a = null;
String b = "";

boolean equal = Objects.equals(a,b); // false

See : https://docs.oracle.com/javase/8/docs/api/java/util/Objects.html#equals-java.lang.Object-java.lang.Object-

    /**
     * Returns {@code true} if the arguments are equal to each other
     * and {@code false} otherwise.
     * Consequently, if both arguments are {@code null}, {@code true}
     * is returned and if exactly one argument is {@code null}, {@code
     * false} is returned.  Otherwise, equality is determined by using
     * the {@link Object#equals equals} method of the first
     * argument.
     *
     * @param a an object
     * @param b an object to be compared with {@code a} for equality
     * @return {@code true} if the arguments are equal to each other
     * and {@code false} otherwise
     * @see Object#equals(Object)
     */
    public static boolean equals(Object a, Object b) {
        return (a == b) || (a != null && a.equals(b));
    }

No files, tests, or entry points are named. Start by locating the Java recipe definitions and their tests, then confirm how existing recipes express equality replacements; done means the recipe identifies nullable object.equals calls and safely replaces them with Objects.equals without changing non-null behavior.