</field>
        <field>
          <name>file</name>
          <version>1.0.0</version>
          <description><![CDATA[
             Specifies that this profile will be activated based on existence of a file.
             ]]></description>
          <association>
            <type>ActivationFile</type>
          </association>
        </field>
      </fields>
    </class>

        if (parentCache != null && parentCache.isComplete()) {
            boolean exists = parentCache.hasChild(getName());
            log.debug("Using cached existence check for: {}", getPath());
            return exists;
        }
    }
    
    // Fall back to regular existence check
    return super.exists();
}

private void requestDirectoryLease() {
    if (!isDirectory() || !context.getConfig().isUseDirectoryLeasing()) {

	if value != nil || !exists {
		t.Fatalf("unexpected value or existence flag for key1: value=%v, exists=%v", value, exists)
	}

	// Adding an entry with the same key but different value
	newVal := "val1"
	lc.Add("key1", &newVal)

	value, exists = lc.Get("key1")
	if value != &newVal || !exists {
		t.Fatalf("unexpected value or existence flag for key1: value=%v, exists=%v", value, exists)
	}
}

            assertTrue(type >= 0, "Type should be non-negative");
        }

        @Test
        @DisplayName("exists should indicate resource existence")
        void testExists() throws CIFSException {
            // Given
            when(mockResource.exists()).thenReturn(true);

            // When
            boolean exists = mockResource.exists();

          </association>
        </field>
        <field>
          <name>file</name>
          <version>1.0.0+</version>
          <description>
            Specifies that this profile will be activated based on existence of a file.
          </description>
          <association>
            <type>ActivationFile</type>
          </association>
        </field>
        <field>
          <name>packaging</name>

	local DATA_DRIVE=-1
	local FILE=$1
	local DIR=$2
	# Check for existence of file in erasure set 1
	docker exec resiliency-minio1-1 /bin/sh -c "stat /data1/test-bucket/$DIR/$FILE/xl.meta" >/dev/null 2>&1
	STATUS=$?
	if [ $STATUS -eq 0 ]; then
		DATA_DRIVE=1
	fi

	if [ $DATA_DRIVE -eq -1 ]; then
		# Check for existence of file in erasure set 2

        return getPackaging().language();
    }

    /**
     * {@return the project POM artifact}, which is the artifact of the POM of this project. Every project have a POM
     * artifact, even if the existence of backing POM file is NOT a requirement (i.e. for some transient projects).
     *
     * @see org.apache.maven.api.services.ArtifactManager#getPath(Artifact)
     */
    @Nonnull

   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.

	// binary's ModTime as release time:
	return getModTime(os.Args[0])
}

// IsDocker - returns if the environment minio is running in docker or
// not. The check is a simple file existence check.
//
// https://github.com/moby/moby/blob/master/daemon/initlayer/setup_unix.go
// https://github.com/containers/podman/blob/master/libpod/runtime.go
//
//	"/.dockerenv":        "file",

   * ImmutableEnumSet/ImmutableSortedSet, regardless of implementation type. It
   * captures their "logical contents" and they are reconstructed using public
   * static factories. This is necessary to ensure that the existence of a
   * particular implementation type is an implementation detail.
   */
  @J2ktIncompatible // serialization
  private static final class SerializedForm implements Serializable {
    final Object[] elements;