*       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

 * the {@link Futures#catching(ListenableFuture, Class, com.google.common.base.Function)
 * Futures.catching} family of methods. Those versions have slightly different signatures.
 */
abstract class GwtFuturesCatchingSpecialization {
  /*
   * In the GWT versions of the methods (below), every exceptionType parameter is required to be
   * Class<Throwable>. To handle only certain kinds of exceptions under GWT, you'll need to write

        // Verify required methods exist
        try {
            CustomSizeValidator.class.getMethod("initialize", CustomSize.class);
            CustomSizeValidator.class.getMethod("isValid", CharSequence.class, ConstraintValidatorContext.class);
            assertTrue("Required methods exist", true);
        } catch (final NoSuchMethodException e) {
            fail("Required methods should exist: " + e.getMessage());
        }

 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.artifact.metadata;

/**
 * Contains metadata about an artifact, and methods to retrieve/store it from an artifact repository.
 */
@Deprecated
public interface ArtifactMetadata extends org.apache.maven.repository.legacy.metadata.ArtifactMetadata {
    void merge(ArtifactMetadata metadata);

 * would require complex stubbing of static methods.  Instead the tests
 * concentrate on the instance methods and simple static predicates
 * that are observable without network access.
 */
@ExtendWith(MockitoExtension.class)
class UniAddressTest {

    /* ---------------------------------------------------------------------
     * 0. Helper methods for parameterised tests

 * callers. Instead, accept {@link Iterable} and have your method or constructor body pass it to the
 * appropriate {@code copyOf} method itself.
 *
 * <p>Expressing the immutability guarantee directly in the type that user code references is a
 * powerful advantage. Although Java offers certain immutable collection factory methods, such as
 * {@link Collections#singleton(Object)} and <a

import org.jspecify.annotations.Nullable;

/**
 * An extension of {@code DataInput} for reading from in-memory byte arrays; its methods offer
 * identical functionality but do not throw {@link IOException}.
 *
 * <p><b>Warning:</b> The caller is responsible for not attempting to read past the end of the
 * array. If any method encounters the end of the array prematurely, it throws {@link

        int result = response.writeSetupWireFormat(null, 0);
        assertEquals(0, result);

        result = response.writeParametersWireFormat(null, 0);
        assertEquals(0, result);

        result = response.writeDataWireFormat(null, 0);
        assertEquals(0, result);
    }

    @Test
    @DisplayName("Test all read methods with null buffer")

  protected ForwardingObject() {}

  /**
   * Returns the backing delegate instance that methods are forwarded to. Abstract subclasses
   * generally override this method with an abstract method that has a more specific return type,
   * such as {@link ForwardingSet#delegate}. Concrete subclasses override this method to supply the
   * instance being decorated.
   */
  protected abstract Object delegate();

     * The {@linkplain State#TERMINATED TERMINATED} state is a terminal state in the transition
     * diagram. Therefore, if this method is called, no other methods will be called on the {@link
     * Listener}.
     *
     * @param from The previous state that is being transitioned from. Failure can occur in any