* Project configuration

 At the project level all configuration is achieved by tweaking the POM. One of the differences between
 maven 1.x and 2.x is that all project parameterization occurs in the POM and not from properties
 files.

 For many of the more advanced features in Maven2 it is critical that POMs be available in the local repository.

  future. Therefore, we should rename this file from pom.xml in the maven-core
  jarfile to pom-4.0.0.xml (and successive revisions to the base pom made to
  accommodate changes in the model will be named accordingly - 4.0.1, 4.0.2, ...).

Minimum Element-Set for a Project POM

  In order to furnish a basic set of information which we need to distinguish one

                }
                // 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(),

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

            assertEquals(0, result, "Apply should succeed for multi-module project");

            // Verify both POMs exist (they may or may not be modified depending on strategies)
            assertTrue(Files.exists(parentPom), "Parent POM should exist");
            assertTrue(Files.exists(modulePom), "Module POM should exist");
        }
    }

    @Nested
    @DisplayName("Error Handling")
    class ErrorHandlingTests {

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;

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

    /**

        // Should have both consumer POM (no classifier) and build POM (with "build" classifier)
        Collection<Artifact> artifacts = result.getArtifacts();
        assertEquals(3, artifacts.size()); // original jar + consumer pom + build pom

        assertTrue(artifacts.stream().anyMatch(a -> "pom".equals(a.getExtension()) && "".equals(a.getClassifier())));
        assertTrue(

h4. Working with POMs during development

During the development of a plugin we would want to make it easy for a developer to create a plugin which means we would allow the direct use of a POM to state the dependencies of a given plugin and any tooling we created would be responsible for turning the dependency information in the POM into plugin metadata which described the dependencies of the plugin.

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