id("gradlebuild.detekt")
    id("gradlebuild.test-retry")
    id("gradlebuild.ci-reporting")
    id("gradlebuild.private-javadoc")
}

description = "A plugin that sets up a Kotlin DSL code that is shared between build-logic and runtime"

java {
    sourceCompatibility = JavaVersion.VERSION_1_8
    targetCompatibility = JavaVersion.VERSION_1_8
}

kotlin {
    compilerOptions {
        allWarningsAsErrors = true

		t.Fatal("no policies found")
	}

	if policies[0] != "consoleAdmin" {
		t.Fatalf("expected 'consoleAdmin', %s", policies[0])
	}
}

// TestSkipContentSha256Cksum - Test validate the logic which decides whether
// to skip checksum validation based on the request header.
func TestSkipContentSha256Cksum(t *testing.T) {
	testCases := []struct {
		inputHeaderKey   string
		inputHeaderValue string

 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

description = "Provides a set of plugins that are shared between the Gradle and build-logic builds"

tasks.register("check") {
    dependsOn(subprojects.map { "${it.name}:check" })

 This is the model for Maven toolchain in <<<org.apache.maven.toolchain>>> package,
 delegating content to {{{../../api/maven-api-toolchain/index.html}Maven 4 API immutable toolchain}}. All the effective model
 building logic from multiple toolchains files is done in {{{../maven-toolchain-builder/}Maven Toolchain Builder}}.

 The following are generated from this model:

 * </pre>
 */
public abstract class AbstractUpgradeStrategy implements UpgradeStrategy {

    /**
     * Template method that handles common logging and error handling.
     * Subclasses implement the actual upgrade logic in doApply().
     */
    @Override
    public final UpgradeResult apply(UpgradeContext context, Map<Path, Document> pomMap) {
        context.info(getDescription());
        context.indent();

        try {

    launcherJar.from(tasks.jar)
    agentJars.from(resolveAgentsClasspath)
    // The trick below is to use the templates from the current code instead of the wrapper. It does not cover the case where the generation logic is updated though.
    unixScriptTemplate.from(layout.projectDirectory.file("../../../platforms/jvm/plugins-application/src/main/resources/org/gradle/api/internal/plugins/unixStartScript.txt"))

 This is strictly the model for Maven POM (Project Object Model) in <<<org.apache.maven.model>>> package,
 delegating content to {{{../../api/maven-api-model/index.html}Maven 4 API immutable model}}. All the effective model
 building logic from multiple POMs and building context is done in {{{../maven-model-builder/}Maven Model Builder}}.

 The following are generated from this model:

 * <p>
 * This annotation can be used on static methods to programmatically create and configure
 * beans that will be managed by the dependency injection container. It's particularly
 * useful when the bean creation requires complex logic or when the bean needs to be
 * configured based on runtime conditions.
 * <p>
 * Example usage:
 * <pre>
 * public class Providers {
 *     {@literal @}Provides
 *     {@literal @}Singleton

- [ ] Provide integration tests (under `<subproject>/src/integTest`) to verify changes from a user perspective.
- [ ] Provide unit tests (under `<subproject>/src/test`) to verify logic.
- [ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
- [ ] Ensure that tests pass sanity check: `./gradlew sanityCheck`.
- [ ] Ensure that tests pass locally: `./gradlew <changed-subproject>:quickTest`.

<component name="DependencyValidationManager">
    <!-- The source of truth for this pattern is `build-logic/basics/src/main/kotlin/gradlebuild/basics/PublicApi.kt` file, please keep them in sync -->
    <scope name="Gradle public API"