PomMemoryAnalyzer analyzer = new PomMemoryAnalyzer();
        MavenStaxReader reader = new MavenStaxReader();

        // Find all pom.xml files, excluding those under src/ or target/
        Files.walk(rootDir)
                .filter(path -> path.getFileName().toString().equals("pom.xml"))
                .filter(path -> !containsSrcOrTarget(path))
                .forEach(pomPath -> {
                    try {

 *
 * @deprecated since 4.0.0
 */
@Named
@Singleton
@Deprecated(since = "4.0.0")
public class MavenSecDispatcher extends DefaultSecDispatcher {
    private static final String FILE_NAME = "settings-security4.xml";

    @Inject
    public MavenSecDispatcher(Map<String, Dispatcher> dispatchers) {
        super(dispatchers, configurationFile());
    }

    private static Path configurationFile() {

 * environment. This interface allows users to define and configure
 * Java-related toolchains that can be utilized during the build process
 * in Maven.</p>
 *
 * <p>Java toolchains are defined in the Maven toolchains.xml file and can
 * be referenced in the project's POM file. This enables developers to
 * specify the exact versions of Java tools they wish to use, ensuring
 * consistency across different build environments.</p>
 *

            // Create a temporary directory with a POM file for the test
            Path tempDir = Files.createTempDirectory("apply-test");
            try {
                Path pomFile = tempDir.resolve("pom.xml");
                String pomContent = PomBuilder.create()
                        .groupId("test")
                        .artifactId("test")
                        .version("1.0.0")
                        .build();

* Group configuration

 As far as properties go for an entire build the maven.properties could be placed at
 the top of the group but I'm not really sure how this might work. There could probably
 also be a directory for plugins.xml and maven.properties.

* Project configuration

 At the project level all configuration is achieved by tweaking the POM. One of the differences between

        assertEquals(1, collector2.getProblems().size());
    }

    @Test
    void testAddProblem() {
        ProblemCollector collector = ProblemCollectorFactory.newInstance(null);
        collector.setSource("pom.xml");
        collector.add(Problem.Severity.ERROR, "Error message", 10, 5, null);
        collector.add(Problem.Severity.WARNING, "Warning message", 15, 3, null);

        List<Problem> problems = collector.getProblems();

        Profile profile = new Profile();

        profile.setId(profileXmlProfile.getId());

        profile.setSource("profiles.xml");

        org.apache.maven.profiles.Activation profileActivation = profileXmlProfile.getActivation();

        if (profileActivation != null) {
            Activation activation = new Activation();

import org.apache.maven.toolchain.ToolchainFactory;
import org.apache.maven.toolchain.ToolchainPrivate;
import org.apache.maven.toolchain.model.ToolchainModel;
import org.codehaus.plexus.util.xml.Xpp3Dom;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

/**
 * JDK toolchain factory.
 * This is a <code>ToolchainFactory</code> Plexus component registered with
 * <code>jdk</code> hint.
 *

			t.Fatal(failTestStr(anonTestStr, fmt.Sprintf("Failed parsing response body: <ERROR> %v", err)))
		}

		actualError := &APIErrorResponse{}
		if err = xml.Unmarshal(actualContent, actualError); err != nil {
			t.Fatal(failTestStr(anonTestStr, "error response failed to parse error XML"))
		}

		if actualError.BucketName != bucketName {
			t.Fatal(failTestStr(anonTestStr, "error response bucket name differs from expected value"))

<?xml version="1.0" encoding="UTF-8"?>

<!--
  ~ Licensed to the Apache Software Foundation (ASF) under one
  ~ or more contributor license agreements.  See the NOTICE file
  ~ distributed with this work for additional information
  ~ regarding copyright ownership.  The ASF licenses this file
  ~ to you under the Apache License, Version 2.0 (the
  ~ "License"); you may not use this file except in compliance