plugins {
    id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin")
}

description = "Provides a plugin to minify and correct metadata for dependencies used by Gradle"

dependencies {
    implementation("gradlebuild:basics")
    implementation(buildLibs.gson)

However, this would limit the ability of the Gradle ecosystem plugin authors to take advantage of new Java features and improvements.

One example is when one of the most popular plugins started requiring Java 17 because the underlying framework behind the plugin began requiring 17, and code from the framework was used in the plugin itself.
What would have happened if Gradle was limited to _only Java 11_ at the time?

 * under the License.
 */
package org.apache.maven.usability.plugin;

import java.io.File;
import java.io.IOException;
import java.io.InputStream;
import java.net.MalformedURLException;
import java.net.URL;
import java.net.URLClassLoader;
import java.util.HashMap;
import java.util.List;
import java.util.Map;

import org.apache.maven.usability.plugin.io.xpp3.ParamdocXpp3Reader;

import org.apache.maven.plugin.descriptor.io.PluginDescriptorStaxReader;
import org.codehaus.plexus.component.repository.ComponentDependency;
import org.codehaus.plexus.component.repository.ComponentRequirement;
import org.codehaus.plexus.configuration.PlexusConfiguration;
import org.codehaus.plexus.configuration.PlexusConfigurationException;

/**
 * Build plugin descriptor object from {@code plugin.xml}.
 *

        title.appendChild(document.createTextNode(" plugin"));

        Element titleabbrev = document.createElement("titleabbrev");
        section.appendChild(titleabbrev);
        literal = document.createElement("literal");
        titleabbrev.appendChild(literal);
        literal.appendChild(document.createTextNode(extension.getPluginId()));
        titleabbrev.appendChild(document.createTextNode(" plugin"));

  <artifactId>testinvalidpom</artifactId>
  <version>0.0.1-SNAPSHOT</version>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>
          <groupId></groupId>
          <artifactId>this-is-the-artifact</artifactId>
        </plugin>
      </plugins>
    </pluginManagement>
  </build>

 * under the License.
 */

/**
 * Contains classes for managing plugin-specific lifecycle bindings and forked executions.
 * This package helps define how plugins can modify or extend Maven's build lifecycle.
 *
 * @since 4.0.0
 */

        // Third parties tasks

        // Publish plugin
        task.name == "login" -> true

        // Kotlin/JS
        // https://youtrack.jetbrains.com/issue/KT-50881
        task.name in listOf("generateExternals") -> true

        // JMH plugin
        task.name in listOf("jmh", "jmhJar", "jmhReport") -> true

        // Gradle Doctor plugin
        task.name in listOf(
            "graph", "graphMain",

[Checkstyle]: https://plugins.jetbrains.com/plugin/1065-checkstyle-idea
[spotless]: https://github.com/diffplug/spotless
[Eclipse Code Formatter]: https://plugins.jetbrains.com/plugin/6546-eclipse-code-formatter

            applyDefaultSettings(artifactRuleOverride = "")

            params {
                // Disable jdk-provider-plugin, otherwise the JAVA_HOME will be overwritten
                // https://github.com/gradle/teamcity-jdk-provider-plugin/blob/main/teamcity-jdk-provider-plugin-agent/src/main/kotlin/org/gradle/teamcity_jdk_provider_plugin/JdkProviderAgentLifecycleListener.kt#L22
                param("JdkProviderEnabled", "false")