* // Document is automatically updated
 * </pre>
 */
public interface UpgradeStrategy {

    /**
     * Applies the upgrade strategy to all eligible POMs.
     *
     * @param context the upgrade context
     * @param pomMap map of all POM files in the project (domtrip Documents)
     * @return the result of the upgrade operation
     */
    UpgradeResult apply(UpgradeContext context, Map<Path, Document> pomMap);

    /**
     * Gets the POM file of the project to build.
     *
     * @return The POM file of the project or {@code null} if not applicable (i.e. when processing a POM from the
     *         repository).
     */
    File getPomFile();

    /**
     * Sets the POM file of the project to build. Note that providing the path to a POM file via this method will make

         * unique within a single POM. Upon multiple declarations, 2.x just kept the last one but retained the order of
         * the first occurrence. So when we're in lenient/compat mode, we have to deal with such broken POMs and mimic
         * the way 2.x works. When we're in strict mode, the removal of duplicates just saves other merging steps from

import org.eclipse.aether.installation.InstallRequest;

import static java.util.Objects.requireNonNull;

/**
 * Inliner POM transformer. The goal of this transformer is to fix Maven 3 issue about emitting (installing, deploying)
 * unusable POMs when using CI Friendly Versions.
 *
 * @since TBD
 */
@Singleton
@Named
class PomInlinerTransformer extends TransformerSupport {

    private static String getArchivesBaseName(ExtensionContainer extensions) {
        return extensions.getByType(BasePluginExtension.class).getArchivesName().get();
    }

    /**
     * Configuration generation of maven poms.
     */
    private void configurePomGeneration(Project project) {
        var gitInfo = project.getRootProject().getPlugins().apply(GitInfoPlugin.class).getGitInfo();

        if (!flattenEnabled) {
            // When flattening is disabled, treat non-POM projects like parent POMs
            // Apply only basic transformations without flattening dependency management
            // However, BOMs still need special handling to transform packaging from "bom" to "pom"
            if (isBom) {
                return buildBomWithoutFlatten(session, project, src);
            } else {

                }
                // If deployBuildPom is false, we simply don't add the build POM to the result
            }
            for (Artifact consumer : consumers) {
                result.remove(consumer);
                // Replace the consumer POM as the main POM (no classifier)
                result.add(new DefaultArtifact(
                        consumer.getGroupId(),

import org.apache.maven.settings.Proxy;
import org.apache.maven.settings.Server;

/**
 * A resolution request allows you to either use an existing MavenProject, or a coordinate (gid:aid:version)
 * to process a POMs dependencies.
 *
 */
@Deprecated
public class ArtifactResolutionRequest implements RepositoryRequest {
    private static final String LS = System.lineSeparator();

    private Artifact artifact;

            Files.createDirectories(tempPomPath.getParent());

            // Write POM to temp location
            writePomToFile(document, tempPomPath);
            context.debug("Wrote POM to temp location: " + tempPomPath);
        }

        return tempDir;
    }

    /**
     * Finds the common root directory of all POM paths.
     */
    private Path findCommonRoot(Set<Path> pomPaths) {

 */
@Experimental
@Immutable
public interface ProjectBuilderRequest extends RepositoryAwareRequest {

    /**
     * Gets the path to the project to build.
     * This is typically the path to a pom.xml file or a directory containing a pom.xml file.
     *
     * @return an optional containing the path to the project, or empty if not specified
     */
    @Nonnull
    Optional<Path> getPath();

    /**