logger.debug("Resolving plugin prefix {} from {}", request.getPrefix(), request.getPluginGroups());

        Model pom = request.getPom();
        Build build = pom != null ? pom.getBuild() : null;
        PluginManagement management = build != null ? build.getPluginManagement() : null;

        // map of groupId -> Set(artifactId) plugin candidates:

package clause

// From from clause
type From struct {
	Tables []Table
	Joins  []Join
}

// Name from clause name
func (from From) Name() string {
	return "FROM"
}

// Build build from clause
func (from From) Build(builder Builder) {
	if len(from.Tables) > 0 {
		for idx, table := range from.Tables {
			if idx > 0 {
				builder.WriteByte(',')
			}

			builder.WriteQuoted(table)
		}
	} else {

          # cache: "pip"
          # cache-dependency-path: pyproject.toml
      - name: Install build dependencies
        run: pip install build
      - name: Build distribution
        env:
          TIANGOLO_BUILD_PACKAGE: ${{ matrix.package }}
        run: python -m build
      - name: Publish
        uses: pypa/gh-action-pypi-publish@v1.13.0
      - name: Dump GitHub context
        env:

        val (buildResult, failure) = try {
            runner.build()!! to null
        } catch (ex: UnexpectedBuildFailure) {
            ex.buildResult!! to ex
        }

        println(buildResult.output)

        val richReportFile = inputBuildDir.resolve("binary-compatibility/build/japi/japi.html").apply {
            assertTrue("Rich report file doesn't exist", isFile)
        }

### Enterprise integration

Provides cross-cutting integration with Gradle's commercial product.

### IDE integration

Provides cross-cutting integration with IDEs and other tooling.

### Build infrastructure

Provides build logic, libraries, test suites and infrastructure to support developing and releasing Gradle.

### Documentation

# Gradle runtimes

Gradle is made up of the following processes that work together to "run the build":

- Gradle daemon. This is the process that actually runs the build. It hosts build logic and coordinates the lifecycle of the build. It is a long-running daemon process.
- CLI client. This is the `gradle` or `gradlew` command, and is responsible for locating, starting and interacting with the Gradle daemon, potentially downloading the Gradle distribution. 

        Element root = doc.root();
        Element build = root.child("build").orElse(null);
        assertNotNull(build, "build should exist");

        // Insert elements in build according to build ordering
        DomUtils.insertContentElement(build, "directory", "target");
        DomUtils.insertContentElement(build, "sourceDirectory", "src/main/java");

        String xmlOutput = DomUtils.toXml(doc);

        RequestData data1 = RequestDataBuilder.newRequestData().method("get").build();
        assertEquals(Method.GET, data1.getMethod());

        RequestData data2 = RequestDataBuilder.newRequestData().method("GET").build();
        assertEquals(Method.GET, data2.getMethod());

        RequestData data3 = RequestDataBuilder.newRequestData().method("post").build();
        assertEquals(Method.POST, data3.getMethod());

        List<ToolchainModel> toolchainModels = List.of(
                ToolchainModel.newBuilder().type("basic").build(),
                ToolchainModel.newBuilder().type("basic").build(),
                ToolchainModel.newBuilder().type("rare").build());
        Session sessionv4 = mock(Session.class);
        when(session.getSession()).thenReturn(sessionv4);

                                    // If we don't clean that up there might be leftover json files from other report builds running on the same machine.
                                    """
                                    results/performance/build/test-results-*.zip!performance-tests/report/css/*.css => $performanceResultsDir/
                                    $perfResultArtifactRule