<version>1.0.0+</version>
          <type>String</type>
          <description>
            The name of the file that should be missing to activate a profile. Please note, that missing and exists
            fields cannot be used together. Only one of them should be used at any one time.
          </description>
        </field>
        <field>
          <name>exists</name>
          <version>1.0.0+</version>

 *
 * @since 4.0.0
 */
@Experimental
public enum CacheRetention {
    /**
     * Data should be persisted across Maven invocations.
     * Suitable for:
     * - Dependency resolution results
     * - Compilation outputs
     * - Downloaded artifacts
     */
    PERSISTENT,

    /**
     * Data should be retained for the duration of the current Maven session.
     * Suitable for:
     * - Build-wide configuration

     * This is an alternative to specifying a path, allowing the project to be built from
     * a model source such as a string or input stream.
     *
     * @return an optional containing the source of the project, or empty if not specified
     */
    @Nonnull
    Optional<Source> getSource();

    /**
     * Determines whether a stub model should be allowed when the POM is missing or unreadable.

        // Then
        assertNotNull(nonce1, "First nonce should not be null");
        assertNotNull(nonce2, "Second nonce should not be null");
        assertEquals(16, nonce1.length, "GCM nonce should be 16 bytes");
        assertEquals(16, nonce2.length, "GCM nonce should be 16 bytes");
        assertFalse(Arrays.equals(nonce1, nonce2), "Consecutive nonces should be different");
    }

    @Test

        // Test with negative integer (two's complement)
        byte[] negativeBytes = new byte[] { (byte) 0xFF, (byte) 0xFF, (byte) 0xFF, (byte) 0xFF }; // Represents -1
        AvFlags negativeAvFlags = new AvFlags(negativeBytes);
        assertNotNull(negativeAvFlags, "AvFlags object should not be null for negative bytes");
        assertEquals(-1, negativeAvFlags.getFlags(), "Flags should be -1 for all FF bytes");
    }

   * file. If they were instead private, then we wouldn't be able to access them reflectively from
   * within VarHandleAtomicHelper and AtomicReferenceFieldUpdaterAtomicHelper.
   *
   * Package-private "shouldn't" be necessary: The *AtomicHelper classes and AbstractFutureState
   * "should" be nestmates, so a call to MethodHandles.lookup or

/**
 * This class uses a static {@link java.util.Properties} to act
 * as a cental repository for all jCIFS configuration properties. It cannot be
 * instantiated. Similar to <code>System</code> properties the namespace
 * is global therefore property names should be unique. Before use,
 * the <code>load</code> method should be called with the name of a
 * <code>Properties</code> file (or <code>null</code> indicating no

  /**
   * Returns a request that includes a credential to satisfy an authentication challenge in
   * [response]. Returns null if the challenge cannot be satisfied.
   *
   * The route is best effort, it currently may not always be provided even when logically
   * available. It may also not be provided when an authenticator is re-used manually in an
   * application interceptor, such as when implementing client-specific retries.
   */

 *
 * <ol>
 *   <li>remove();
 *   <li>hasNext()
 *   <li>hasNext();
 *   <li>remove();
 *   <li>next();
 * </ol>
 *
 * <p>This particular order of operations may be unrealistic, and testing all 3^5 of them may be
 * thought of as overkill; however, it's difficult to determine which proper subset of this massive

  Note that commits might be squashed by a maintainer on merge.
- [ ] Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
- [ ] Run `mvn verify` to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.