}

    public void test_multipleSessionsIndependence() {
        // Setup
        String session1 = "session1";
        String session2 = "session2";

        // Add different filters for different sessions
        service.addIncludeUrlFilter(session1, "https://session1.com/.*");
        service.addIncludeUrlFilter(session2, "https://session2.com/.*");

            invoke(fs.getPath("/cwd"), fs.getPath("/home"), List.of("verify"), List.of());
        }
    }

    /**
     * Same source (user or project extensions.xml) must not contain same GA with different V.
     */
    @Test
    void conflictingExtensionsFromSameSource(
            @TempDir(cleanup = CleanupMode.ON_SUCCESS) Path cwd,
            @TempDir(cleanup = CleanupMode.ON_SUCCESS) Path userHome)

            when(parent.getLocator()).thenReturn(locator);
            when(locator.getURL()).thenReturn(new URL("file:/"));
            // Throw CIFSException with different cause
            CIFSException differentException = new CIFSException("different error");
            when(locator.getAddress()).thenThrow(differentException);

            // Act + Assert

    Property<String> getSomeProperty()
}
class Example {
    Property<NestedType> getNestedProperty()
}
```

This is unnecessary because users will have trouble creating instances of `NestedType` and merging different instances of `NestedType`. It's also more awkward for users to access the properties in the nested property.

If the nested type is a managed type (Gradle can generate its implementation), you can define a nested property with:
```

 *   <li>{@link org.apache.maven.api.cache.CacheMetadata} - Configuration for cache behavior and lifecycle</li>
 * </ul>
 * <p>
 * The caching system supports different retention periods through {@link org.apache.maven.api.cache.CacheRetention}:
 * <ul>
 *   <li>PERSISTENT - Data persists across Maven invocations</li>
 *   <li>SESSION_SCOPED - Data retained for the duration of a Maven session</li>

import org.apache.maven.model.building.ModelProblemCollector;

/**
 * Handles normalization of a model. In this context, normalization is the process of producing a canonical
 * representation for models that physically look different but are semantically equivalent.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface ModelNormalizer {

    /**

   */
  boolean serializable() default false;

  /**
   * When {@code true}, the annotated type is emulated in GWT. The emulated source (also known as
   * super-source) is different from the implementation used by the JVM.
   *
   * @see <a href=
   *     "https://www.gwtproject.org/doc/latest/DevGuideOrganizingProjects.html#DevGuideModules">
   *     Documentation about GWT emulated source</a>
   */

  public void testForEachKnownOrder() {
    List<E> elements = new ArrayList<>();
    collection.forEach(elements::add);
    List<E> expected = copyToList(getOrderedElements());
    assertEquals("Different ordered iteration", expected, elements);
  }

 * Outer class that exists solely to let us write {@code Partially.GwtIncompatible} instead of plain
 * {@code GwtIncompatible}. This is more accurate for {@link Futures#catching}, which is available
 * under GWT but with a slightly different signature.
 *
 * <p>We can't use {@code PartiallyGwtIncompatible} because then the GWT compiler wouldn't recognize
 * it as a {@code GwtIncompatible} annotation. And for {@code Futures.catching}, we need the GWT

                .repositories(repositories2)
                .build();

        ArtifactResolverRequest request3 = builder.session(session)
                .coordinates(Arrays.asList(coords2, coords1)) // Different order
                .repositories(repositories1)
                .build();

        // Test equals and hashCode
        assertEquals(request1, request2);
        assertEquals(request1.hashCode(), request2.hashCode());