PropertiesUtil.load(properties, inputStreamReader);
    }

    /**
     * Test method for
     * {@link org.codelibs.core.io.PropertiesUtil#load(Properties, File)} .
     */
    @Test
    public void testLoadPropertiesFile() {
        final Properties properties = new Properties();
        PropertiesUtil.load(properties, inputFile);

 *
 * <h3>Projects</h3>
 *
 * <p>{@link org.apache.maven.api.Project} instances are loaded by Maven from the local
 * file system (those projects are usually about to be built) or from the local repository
 * (they are usually downloaded during dependency collection). Those projects are loaded
 * from a Project Object Model (POM).</p>
 *

        bindingMap.put("container", SingletonLaContainerFactory.getContainer());

        // Create GroovyShell with custom class loader for proper resource management
        GroovyClassLoader classLoader = null;
        try {
            // Get parent class loader with fallback to ensure robustness across threading contexts
            ClassLoader parentClassLoader = Thread.currentThread().getContextClassLoader();

                                continue;
                            }

                            /*
                             * An include was loaded successfully. We can skip
                             * all other includes up to the #END_ALTERNATE tag.
                             */

                            while ((line = br.readLine()) != null) {

import org.junit.jupiter.api.Test;

/**
 * Tests for the KerberosConstants interface.
 */
class KerberosConstantsTest {

    /**
     * This test primarily exists to ensure the constants interface can be loaded
     * and to provide a basic check of its values.
     * Since it's an interface with only static final fields, there is no complex logic to test.
     */
    @Test
    void testConstants() {

replace-schema-*.sql:
DDL statements for creation of your schema.
You should write your own DDL statements in this file.
(A SQL separator is semicolon ";")

take-finally-*.sql:
SQL statements for check loaded data (or DDL after data loading)
You should write your own SQL statements in this file.
(basically same specifications as replace-schema.sql)

The "data" directory is for data loading like this:

 *   <li>Configure whether to use the filename for MIME type detection when the stream is octet-stream.</li>
 * </ul>
 *
 * <p>
 * The MIME type detection is based on the {@code tika-mimetypes.xml} resource, which is loaded during initialization.
 * </p>
 *
 * <p>
 * Usage:
 * </p>
 * <pre>
 * MimeTypeHelperImpl mimeTypeHelper = new MimeTypeHelperImpl();
 * String contentType = mimeTypeHelper.getContentType(inputStream, filename);

		if users2[idx].Manager == nil {
			t.Fatalf("Failed to load Manager")
		}
		// manager
		CheckUser(t, *user.Manager, *users2[idx].Manager)
		// user pet
		if users2[idx].NamedPet == nil {
			t.Fatalf("Failed to load NamedPet")
		}
		CheckPet(t, *user.NamedPet, *users2[idx].NamedPet)
		// manager pet
		if users2[idx].Manager.NamedPet == nil {
			t.Fatalf("Failed to load NamedPet")
		}

    /**
     * Updates the context class loader such that the container will search the project realm when the model builder
     * injects the lifecycle bindings from the packaging in the next step. The context class loader is to be reset by
     * the project builder when the project is fully assembled.
     *

    Extension descriptor, stored in <code>META-INF/maven/extension.xml</code> in an extension's jar artifact to
    precisely control parts of the extension and dependencies to expose in the API class loader.
    Maven uses Plexus Classworlds to build the class loader hierarchy, therefore some concepts used in this extensions
    stem from Plexus Classworlds originally.