// TODO Should this be changed for MNG-6754 too?
            snapshot.setTimestamp(getDeploymentTimestamp());

            // we update the build number anyway so that it doesn't get lost. It requires the timestamp to take effect
            try {
                int buildNumber = resolveLatestSnapshotBuildNumber(artifact, localRepository, remoteRepository);

                snapshot.setBuildNumber(buildNumber + 1);

        msgs.add("* An aggregator Mojo is already executing in parallel build,    *");
        msgs.add("* but aggregator Mojos require exclusive access to reactor to   *");
        msgs.add("* prevent race conditions. This mojo execution will be blocked  *");
        msgs.add("* until the aggregator work is done.                            *");
        msgs.add("*****************************************************************");

        if (finishImmediately) {
            projectBuildFutureTask.run();
        }
        return projectBuildFutureTask;
    }

    public Future<ProjectSegment> take() throws InterruptedException {
        return null;
    }

    public Future<ProjectSegment> poll() {
        return null;
    }

  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-2006</name>
  <description>
    Test that inheritance of those URLs which automatically append the child's artifact id take the child's
    relative location to the parent into account.
  </description>

  <modules>
    <module>../child</module>
  </modules>

  <url>https://project.url/parent</url>

  <scm>

------------

If you are interested in the development of Maven, please consult the
documentation first and afterward you are welcome to join the developers
mailing list to ask questions or discuss new ideas/features/bugs etc.

Take a look into the [contribution guidelines](CONTRIBUTING.md).

License
-------
This code is under the [Apache License, Version 2.0, January 2004][license].

    // 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 plugins in the default lifecycle and create
    // fully populated Plugin objects, including executions with goals and default configuration taken
    // from the plugin.xml inside a plugin.
    //