context.indent();
            context.info("Processed: " + result.processedPoms().size() + " POMs");
            context.info("Modified: " + result.modifiedPoms().size() + " POMs");
            context.failure("Errors: " + result.errorPoms().size() + " POMs");
            context.unindent();
        } else if (!result.modifiedPoms().isEmpty()) {

            assertEquals(0, result.processedPoms().size(), "Should have no processed POMs");
            assertEquals(0, result.modifiedPoms().size(), "Should have no modified POMs");
            assertEquals(0, result.errorPoms().size(), "Should have no error POMs");
        }

        @Test
        @DisplayName("should handle overlapping POM modifications")

@Measurement(time = 10)
public class Xpp3DomPerfTest {
    @State(Scope.Benchmark)
    public static class AdditionState {
        List<Path> poms;

        @Setup(Level.Iteration)
        public void setUp() throws IOException {
            Path userHome = Paths.get(System.getProperty("user.home"));
            poms = Files.walk(userHome.resolve(".m2/repository/org/apache/maven"))
                    .filter(p -> p.getFileName().toString().endsWith(".pom"))

 * Subclasses only differ in whether they save modifications to disk.
 *
 * <h2>Supported Upgrades</h2>
 *
 * <h3>Model Version Upgrades</h3>
 * <ul>
 *   <li><strong>4.0.0 → 4.1.0</strong>: Upgrades Maven 3.x POMs to Maven 4.1.0 format</li>
 * </ul>
 *
 * <h3>4.0.0 → 4.1.0 Upgrade Process</h3>
 * <ol>
 *   <li><strong>Namespace Update</strong>: Changes namespace from Maven 4.0.0 to 4.1.0 for all elements</li>

        return new Parser().parse(content);
    }

    /**
     * Recursively discovers module POMs from the given parent POM.
     *
     * @param baseDirectory the base directory for resolving module paths
     * @param parentPom the parent POM document
     * @param pomMap the map to store discovered POMs
     * @throws IOException if there's an error reading files
     * @throws DomTripException if there's an error parsing XML

 * are validated to ensure they don't contain duplicates or null entries.
 *
 * <p>Remote repositories are used for:
 * <ul>
 *   <li>Resolving artifacts and their metadata</li>
 *   <li>Downloading parent POMs and dependency POMs</li>
 *   <li>Retrieving version information and ranges</li>
 *   <li>Accessing plugin artifacts and their dependencies</li>
 * </ul>
 *
 * <p>Repository validation ensures data integrity by:
 * <ul>

            assertTrue(duration < 5000, "Artifact computation should complete within 5 seconds for 100 POMs");

            // Verify correctness
            assertNotNull(gavs, "Artifact set should not be null");
            assertEquals(100, gavs.size(), "Should have computed GAVs for all 100 POMs");
        }
    }

            return null;
        }

        return Coordinates.of(groupId, artifactId, version);
    }

    /**
     * Computes all artifacts from all POMs in a multi-module project.
     * This includes resolving parent inheritance.
     *
     * @param context the upgrade context for logging
     * @param pomMap map of all POM files in the project

 * Maven POM files and resolving related project POMs.
 *
 * <p>The interface provides two types of sources:</p>
 * <ul>
 *   <li>Build sources: Used for POM files of projects being built by Maven in the filesystem.
 *       These sources support resolving related POMs using the {@link ModelLocator}.</li>

 * <ul>
 *   <li>Path sources - simple access to file content</li>
 *   <li>Build sources - POM files being actively built by Maven</li>
 *   <li>Resolved sources - POMs resolved from repositories</li>
 * </ul>
 *
 * @since 4.0.0
 */
@Experimental
public final class Sources {

    private Sources() {}

    /**
     * Creates a new source for the specified path.