* under the License.
 */
package org.apache.maven.lifecycle.providers.packaging;

import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

/**
 * {@code war} packaging plugins bindings provider for {@code default} lifecycle.
 */
@Named("war")
@Singleton
public final class WarLifecycleMappingProvider extends AbstractLifecycleMappingProvider {
    // START SNIPPET: war

            The lists of the remote repositories for discovering plugins.
          </description>
          <association>
            <type>Repository</type>
            <multiplicity>*</multiplicity>
          </association>
          <comment>
            This may be removed or relocated in the near
            future. It is undecided whether plugins really need a remote
            repository set of their own.

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?

            task.getSourceFile().convention(dslReference.getRoot().file("dsl.xml"));
            task.getPluginsMetaDataFile().convention(dslReference.getRoot().file("plugins.xml"));
            task.getClassDocbookDirectory().convention(dslReference.getRoot());
            task.getClassMetaDataFile().convention(dslMetaData.flatMap(ExtractDslMetaDataTask::getDestinationFile));

import ru.vyarus.gradle.plugin.animalsniffer.AnimalSnifferExtension

plugins {
  kotlin("multiplatform")
  id("com.android.kotlin.multiplatform.library")
  kotlin("plugin.serialization")
  id("okhttp.publish-conventions")
  id("okhttp.jvm-conventions")
  id("okhttp.quality-conventions")
  id("okhttp.testing-conventions")
  id("app.cash.burst")
  alias(libs.plugins.maven.sympathy)
}

val copyKotlinTemplates =

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.di.Named;

/**
 * Service provider interface for registering custom {@link Lifecycle} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional build lifecycles
 * beyond the standard ones provided by Maven (like clean, default, site). Lifecycles define a sequence
 * of phases that can be executed during a build.
 * <p>

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.di.Named;

/**
 * Service provider interface for registering custom {@link PathScope} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional path scopes
 * beyond the standard ones provided by Maven. Path scopes define how dependencies are used
 * in different contexts, such as compilation, testing, or runtime.
 * <p>

import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.di.Named;

/**
 * Service provider interface for registering custom {@link Type} implementations.
 * <p>
 * This interface allows plugins and extensions to define and register additional artifact types
 * beyond the standard ones provided by Maven (like jar, war, pom, etc.). Types define how artifacts

        <![CDATA[
    <offline>true</offline>
    ]]></configuration>
      <description>
        <![CDATA[
      Flags the system as offline, to prevent accessing the network to resolve artifacts or execute plugins.

      NOTE: It's also possible to switch to offline mode on a per-build basis, using the '-o' command-line option.
    ]]></description>
    </expression>
    <expression>
      <syntax>settings.interactiveMode</syntax>

        debugDependencyRequirements(executionPlan.getMojoExecutions());

        logger.debug("Repositories (dependencies): " + currentProject.getRemoteProjectRepositories());
        logger.debug("Repositories (plugins)     : " + currentProject.getRemotePluginRepositories());

        for (ExecutionPlanItem mojoExecution : executionPlan) {
            debugMojoExecution(mojoExecution.getMojoExecution());
        }