}
            }
            return acceptOrReject(member, Violation.notBinaryCompatible(member));
        }
        return null;
    }

    // Annotation-related violations are not fully supported by japicmp plugin yet.
    // See https://github.com/melix/japicmp-gradle-plugin/issues/92
    private void removeAnnotationChanges(JApiCompatibility member) {

                "",
                display = ParameterDisplay.PROMPT,
                allowEmpty = false,
                description =
                    "Which performance test to run. Should be the fully qualified class name dot (unrolled) method name. " +
                        "E.g. org.gradle.performance.regression.java.JavaUpToDatePerformanceTest.up-to-date assemble (parallel true)",
            )
            text(

Our codebase uses `null` extensively to represent an absence of value or optionality of the argument.
We utilize nullness annotations in Java code and somewhat rely on IDE warnings to guide us.
However, the Java code we have is not fully annotated, which causes several consequences:
* IDE warnings can be misleading
* Redundant null checks may increase binary size, hurt performance, and increase cognitive load for readers

        when(mockFuture.actionGet(anyLong(), any(TimeUnit.class))).thenReturn(mockHealthResponse);

        // Should not throw NullPointerException
        try {
            // Note: We can't easily test connect() fully without mocking createClient()
            // This test verifies the null check logic indirectly
            final String[] indices = fesenClient.targetIndices != null ? fesenClient.targetIndices : new String[0];

  if expr "$link" : '/.*' > /dev/null; then
    PRG="$link"
  else
    PRG="`dirname "$PRG"`/$link"
  fi
done

saveddir=`pwd`

MAVEN_HOME=`dirname "$PRG"`/..

# make it fully qualified
MAVEN_HOME=`cd "$MAVEN_HOME" && pwd`

cd "$saveddir"

CLASSWORLDS_CONF="$MAVEN_HOME/bin/m2.conf"

# For Cygwin and MinGW, ensure paths are in Unix format before anything is touched

You can then use it as a Gradle Wrapper local distribution in a Gradle based project by using a `file:/` URL pointing to the built distribution:

    ./gradlew wrapper --gradle-distribution-url=file:/path/to/gradle-<version>-bin.zip

To create a full distribution (includes sources and docs):

         */
        public SpnegoConfig() {
            // do nothing
        }

        /**
         * Gets the filter name for this SPNEGO configuration.
         *
         * @return The fully qualified class name of SpnegoAuthenticator
         */
        @Override
        public String getFilterName() {
            return SpnegoAuthenticator.class.getName();
        }

        /**

 * <p>Note that this implementation is not synchronized. If multiple threads access the same cell of
 * an {@code ArrayTable} concurrently and one of the threads modifies its value, there is no
 * guarantee that the new value will be fully visible to the other threads. To guarantee that
 * modifications are visible, synchronize access to the table. Unlike other {@code Table}
 * implementations, synchronization is unnecessary between a thread that writes to one cell and a

                <excludes>
                  <exclude>module-info.java</exclude>
                </excludes>
                <compilerArgs>
                  <!--
                      Make includes/excludes fully work:
                      https://issues.apache.org/jira/browse/MCOMPILER-174
                      (Compare what guava-gwt has to do for maven-javadoc-plugin.)
                  -->
                  <arg>-sourcepath</arg>

                <excludes>
                  <exclude>module-info.java</exclude>
                </excludes>
                <compilerArgs>
                  <!--
                      Make includes/excludes fully work:
                      https://issues.apache.org/jira/browse/MCOMPILER-174
                      (Compare what guava-gwt has to do for maven-javadoc-plugin.)
                  -->
                  <arg>-sourcepath</arg>