* under the License.
 */
package org.apache.maven.project;

import java.io.File;
import java.util.HashMap;
import java.util.Map;

/**
 * Holds all POM files that are known to the reactor. This allows the project builder to resolve imported POMs from the
 * reactor when building another project's effective model.
 */
class ReactorModelPool {

    private final Map<CacheKey, File> pomFiles = new HashMap<>();

        assertNotNull(builder);
        File pom = getPom("simple");

        String originalExists =
                readPom(pom).getProfiles().get(1).getActivation().getFile().getExists();

        DefaultModelBuildingRequest request = new DefaultModelBuildingRequest();
        request.setProcessPlugins(true);
        request.setPomFile(pom);
        ModelBuildingResult result = builder.build(request);

 Hervé Boutemy
 -----
 2011-06-12
 -----

Maven Model

 This is strictly the model for Maven POM (Project Object Model) in <<<org.apache.maven.model>>> package,
 delegating content to {{{../../api/maven-api-model/index.html}Maven 4 API immutable model}}. All the effective model
 building logic from multiple POMs and building context is done in {{{../maven-model-builder/}Maven Model Builder}}.

import org.eclipse.aether.resolution.VersionRangeResult;

/**
 * A model resolver to assist building of dependency POMs. This resolver gives priority to those repositories that have
 * been initially specified and repositories discovered in dependency POMs are recessively merged into the search chain.
 *
 * @see DefaultArtifactDescriptorReader
 * @deprecated since 4.0.0, use {@code maven-api-impl} jar instead
 */

/**
 * A utility class that analyzes Maven POM files to identify memory usage patterns and potential memory optimizations.
 * This analyzer focuses on identifying duplicate strings and their memory impact across different paths in the POM structure.
 *
 * <p>The analyzer processes POM files recursively, tracking string occurrences and their locations within the POM structure.

    /**
     * Returns the target POM model version for upgrades.
     * Supported values include "4.0.0" and "4.1.0".
     *
     * @return an {@link Optional} containing the model version, or empty if not specified
     */
    @Nonnull
    Optional<String> modelVersion();

    /**
     * Returns the directory to use as starting point for POM discovery.
     * If not specified, the current directory will be used.

        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 {

 * // 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);

         * 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 {