def "libraries extension is not visible in buildSrc"() {
        disableProblemsApiCheck()
        settingsFile << """
            dependencyResolutionManagement {
                versionCatalogs {
                    libs {
                        library("lib", "org.gradle.test:lib:1.0")
                    }
                }
            }
        """
        file("buildSrc/build.gradle") << """
            dependencies {

            // this is for parallel execution
            checkDeps.mustRunAfter(rootProject.checkDeps)
        """
        given:
        def supplierInteractions = withPerVersionStatusSupplier(file("buildSrc/src/main/groovy/MP.groovy"))
        otherBuildFile << supplierDeclaration('MP')

        repositoryInteractions {
            'group:projectA' {
                expectVersionListing()
                '1.2' {

// The same approach can be used to resolve plugins from composite builds, which link:https://github.com/gradle/gradle/issues/2528[do not expose plugin markers] yet.
// Simply map the plugin ID to the corresponding artifact coordinates as shown in the Android samples above.


// TODO ?
// [[sec:buildSrc]]
// == Using `buildSrc`
//
// 1. what is buildSrc -> link
// 2. apply the `kotlin-dsl` plugin, see below for the details

        assertTransformed()
    }

    def "buildSrc output may require transform output"() {
        withColorVariants(mavenRepo.module("test", "test", "12")).publish()

        createDirs("buildSrc/producer")
        file("buildSrc/settings.gradle") << """
            include 'producer'
        """
        def buildSrcBuildFile = file("buildSrc/build.gradle")

            }
        """

        settingsFile << """
            include 'consumer'
        """

        // Can't define classes in buildscript block, so let's do it in buildSrc
        file("buildSrc/src/main/groovy/TargetColor.groovy") << """
            import ${TransformParameters.name}
            import ${Property.name}
            import ${Input.name}

==== Init scripts are applied to `buildSrc` builds

Init scripts specified using `--init-script` are now applied to `buildSrc` builds. In previous releases these were applied to included builds but not `buildSrc builds.

This behavior is now consistent for `buildSrc` and included builds.

==== Gradle no longer runs the `build` task for `buildSrc` builds

.Custom task class
====
[source,java]
.buildSrc/src/main/java/org/example/ProcessTemplates.java
----
include::{snippetsPath}/tasks/incrementalBuild-customTaskClass/groovy/buildSrc/src/main/java/org/example/ProcessTemplates.java[tag=custom-task-class]
----

[source,java]
.buildSrc/src/main/java/org/example/TemplateData.java
----

            withProblem("Task `:a:broken` of type `org.gradle.api.DefaultTask`: invocation of 'Task.project' at execution time is unsupported.")
        }
    }

    def "reports problems in buildSrc plugin"() {
        file("buildSrc/src/main/java/SneakyPlugin.java") << """
            import ${Project.name};
            import ${Plugin.name};

            public class SneakyPlugin implements Plugin<Project> {

[[config_cache:not_yet_implemented:testkit_build_with_java_agent]]
=== Using a Java agent with builds run using TestKit

When running builds using <<test_kit#test_kit, TestKit>>, the configuration cache can interfere with Java agents, such as the Jacoco agent, that are applied to these builds.

See link:{gradle-issues}25979[gradle/gradle#25979].

.Creating a unit test report for subprojects
====
include::sample[dir="snippets/testing/testReport/kotlin",files="buildSrc/src/main/kotlin/myproject.java-conventions.gradle.kts[tags=test-report];build.gradle.kts[tags=test-report]"]
include::sample[dir="snippets/testing/testReport/groovy",files="buildSrc/src/main/groovy/myproject.java-conventions.gradle[tags=test-report];build.gradle[tags=test-report]"]
====