assertFalse(filter.include(artifact), "Maven artifact should be excluded by glob pattern");
        assertTrue(filter.include(artifact2), "JUnit artifact should not be excluded by maven-* glob pattern");
    }

    @Test
    void testExcludeWithGlobStar() {
        Exclusion exclusion = new Exclusion();
        exclusion.setGroupId("**");

     *       module path, but is also compatible with placement on the class path. Compatibility can
     *       be achieved, for example, by repeating in the {@code META-INF/services/} directory the services
     *       that are declared in the {@code module-info.class} file. In that case, the path type can be chosen
     *       by the plugin.</li>
     *   <li>If a {@link #patchModule(String)} is also set and the main JAR file is placed on the module path,

It was created to generate the HTML in the backend, not to create APIs used by a modern frontend (like React, Vue.js and Angular) or by other systems (like <abbr title="Internet of Things">IoT</abbr> devices) communicating with it.

* It takes each **request** that comes to your application.
* It can then do something to that **request** or run any needed code.
* Then it passes the **request** to be processed by the rest of the application (by some *path operation*).
* It then takes the **response** generated by the application (by some *path operation*).

They are normally used to declare specific security permissions, for example:

* `users:read` or `users:write` are common examples.
* `instagram_basic` is used by Facebook / Instagram.
* `https://www.googleapis.com/auth/drive` is used by Google.

/// info

In OAuth2 a "scope" is just a string that declares a specific permission required.

It doesn't matter if it has other characters like `:` or if it is a URL.

 *
 * <p>The algorithm calculates a weight for each project as:
 * weight = 1 + max(downstream_project_weights)
 *
 * <p>Projects are then sorted by weight in descending order, ensuring that
 * projects with longer dependency chains are built first. When projects have
 * the same weight, they are ordered by project ID for deterministic results.
 *
 * <p><b>Example:</b>
 * <p>Consider projects with dependencies: A → B → D, A → C → D
 * <ul>

        // Both have same weight (2), so ordering should be by project ID
        // Project B should come before C alphabetically by project ID
        assertEquals(
                ProjectDependencyGraphStub.B,
                projects.get(0),
                "Project B should come before C when they have the same weight (ordered by project ID)");
        assertEquals(
                ProjectDependencyGraphStub.C,

    /**
     * Returned by {@link jcifs.SmbResource#getType()} if the resource this <code>SmbFile</code>
     * represents is a server.
     */
    int TYPE_SERVER = 0x04;
    /**
     * Returned by {@link jcifs.SmbResource#getType()} if the resource this <code>SmbFile</code>
     * represents is a share.
     */
    int TYPE_SHARE = 0x08;
    /**

    }

    @Test
    @DisplayName("Invalid: resolving class by null name throws NPE")
    void testClassForNameWithNull() {
        // Intent: demonstrate defensive behavior with null when resolving this type by name
        assertThrows(NullPointerException.class, () -> Class.forName(null));
    }

    @Test

 * to register, retrieve, and discover available data stores.
 *
 * <p>Data stores are registered by name and class name, allowing flexible lookup.
 * The factory also supports dynamic discovery of data store plugins by scanning
 * JAR files for data store configurations.</p>
 *
 * <p>Thread-safe operations are supported for registration and retrieval of data stores.