this.pluginVersionResolver = pluginVersionResolver;
    }

    public void resolveMissingPluginVersions(MavenProject project, MavenSession session)
            throws PluginVersionResolutionException {
        Map<String, String> versions = new HashMap<>(64);

        for (Plugin plugin : project.getBuildPlugins()) {
            if (plugin.getVersion() == null) {

# CI Pipeline Configuration

## Open & import the project

In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project.

## Project structure

Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.

There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.

    public VagrantExtension(Project project) {
        this.box = project.getObjects().property(String.class);
        this.hostEnv = project.getObjects().mapProperty(String.class, Object.class);
        this.vmEnv = project.getObjects().mapProperty(String.class, Object.class);
        this.vagrantfile = project.getObjects().fileProperty();

## Build logic organisation

The Elasticsearch project contains 3 build-related projects that are included into the Elasticsearch build as a [composite build](https://docs.gradle.org/current/userguide/composite_builds.html).

### `build-conventions`

This project contains build conventions that are applied to all elasticsearch projects.

### `build-tools`

        }
    }

    publications.withType<MavenPublication>().configureEach {
        pom {
            description = provider {
                require(project.description != null) { "You must set the description of published project ${project.name}" }
                project.description
            }
            url = "https://gradle.org"
            licenses {
                license {
                    name = "Apache-2.0"

  val sourceSets = project.extensions.findByType<SourceSetContainer>()
  val main = sourceSets?.findByName("main") ?: sourceSets?.findByName("jvmMain")
  if (main != null) {
    this.sourceSets = listOf(main)
  }

  signatures = androidSignature + jvmSignature
  failWithoutSignatures = false
}

// Default to only published modules
project.tasks.withType<AnimalSniffer> {

import org.apache.maven.plugin.version.PluginVersionResolutionException;
import org.apache.maven.project.MavenProject;

/**
 * @since 3.0
 */
public interface LifecycleExecutionPlanCalculator {
    MavenExecutionPlan calculateExecutionPlan(MavenSession session, MavenProject project, List<Task> tasks)
            throws PluginNotFoundException, PluginResolutionException, LifecyclePhaseNotFoundException,

    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"
    feature: support "project.directory" property, ressembling future model addition of "directory" element along "artifactId"
  </description>

  <properties>
    <project.directory>child</project.directory>
  </properties>

    private final List<MavenProject> transitiveUpstreamProjects;

    public ProjectSegment(MavenProject project, TaskSegment taskSegment, MavenSession copiedSession) {
        this.project = project;
        this.taskSegment = taskSegment;
        this.session = copiedSession;
        final ProjectDependencyGraph dependencyGraph = getSession().getProjectDependencyGraph();

        this.objectFactory = objectFactory;
    }

    @Override
    public void apply(Project project) {
        project.getTasks().withType(Test.class).configureEach(task -> configureTestTask(task, objectFactory));
    }