<build>
        <plugins>
          <plugin>
            <artifactId>plugin-all-profiles</artifactId>
            <executions>
              <execution>
                <id>Active all ||${project.basedir}||</id>
                <configuration>
                  <plugin-all-profiles-in>Active all ||${project.basedir}||</plugin-all-profiles-in>
                </configuration>
              </execution>
            </executions>

 of models you may specify:

 all of the models that you specify are collected to produce a lineage and then the super model is place at
 the top of that lineage to provide default values.

 The super model is where we place all the values which we believe to be standard, values that can be shared and
 utilized across all your Maven projects.

+-----+
 m0 <- m1 <- m2
+-----+

            Other values define only the prefix of classes/resources being exposed. Their binary name must be equal to the prefix or starting with the prefix (followed by "." or "$").

        checkBuildPluginWithArtifactId(
                activeProfilePlugins,
                "plugin-all-profiles",
                "Active all ||${project.basedir}||",
                "<plugin-all-profiles-in>Active all ||${project.basedir}||</plugin-all-profiles-in>");

        checkBuildPluginWithArtifactId(
                activeProfilePlugins,
                "only-active-profile",

 * </p>
 * <p>
 * With changes during 3.2.2 release MavenProject is closer to being immutable after construction with the removal of
 * all components from this class, and the upfront construction taken care of entirely by the {@link ProjectBuilder}.
 * There is still the issue of having to run the lifecycle in order to find all the compile source roots and resource
 * directories but I hope to take care of this during the Maven 4.0 release (jvz).
 * </p>
 */

    // together and this really shows the problem of constructing a sensible default configuration but
    // it's all encapsulated here so it appears normalized to the POM builder.

    // We are going to take the project packaging and find all plugin in the default lifecycle and create
    // fully populated Plugin objects, including executions with goals and default configuration taken

        this(projects, projects);
    }

    /**
     * Creates a new project dependency graph based on the specified projects.
     *
     * @param allProjects All collected projects.
     * @param projects    The projects to create the dependency graph with.
     * @throws DuplicateProjectException
     * @throws CycleDetectedException
     * @since 3.5.0

Copyright (c) 2008 FasterXML LLC ******@****.***

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the

  <version>1.0-SNAPSHOT</version>

  <name>Maven Integration Test :: MNG-3760</name>
  <description>
    Test interpolation of ${project.baseUri}
  </description>

  <properties>
    <!-- this is where we collect all the interpolated values for the POM dump -->
    <prop1>${project.baseUri}</prop1>
  </properties>