<scope>runtime</scope>
    </dependency>
  </dependencies>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>

      <version>1.0</version>
    </dependency>
  </dependencies>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <configuration>
          <tasks><echo>${project.parent.basedir}</echo></tasks>
        </configuration>
      </plugin>
    </plugins>
  </build>

 */
package org.apache.maven.api.plugin;

import java.util.List;

import org.apache.maven.api.annotations.Consumer;
import org.apache.maven.api.annotations.Experimental;
import org.apache.maven.api.plugin.descriptor.lifecycle.Lifecycle;

/**
 * Interface that can be provided by the plugin to wire in custom lifecycles
 * leveraged using the {@link org.apache.maven.api.plugin.annotations.Execute}

 User configuration which is utilized at the project level are controlled with the
 ${project.home}/maven.properties file.

Plugin configuration

 The configuration of plugins is of the same form as the maven {{{plugin-descriptors}plugin descriptors}}
 themselves:

+-----+
<plugins>
  <plugin>
   <id>xdoc</id>
   <version>1.0</version>
   <parameters>
     <parameter>
       <name>theme</name>

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

import java.util.Map;

/**
 * Interface to allow <code>Mojos</code> to communicate with each others <code>Mojos</code>, other than
 * project's source root and project's attachment.<br>
 * The plugin manager would pull the context out of the plugin container context, and populate it into the Mojo.
 *
 */
public interface ContextEnabled {

import org.apache.maven.model.plugin.DefaultPluginConfigurationExpander;
import org.apache.maven.model.plugin.DefaultReportConfigurationExpander;
import org.apache.maven.model.plugin.DefaultReportingConverter;
import org.apache.maven.model.plugin.LifecycleBindingsInjector;
import org.apache.maven.model.plugin.PluginConfigurationExpander;
import org.apache.maven.model.plugin.ReportConfigurationExpander;

package gradlebuild.integrationtests.androidhomewarmup

import org.gradle.api.Plugin
import org.gradle.api.Project
import org.gradle.kotlin.dsl.register

/**
 * Plugin that pre-downloads Android SDK components to prevent race conditions during parallel builds.
 *
 * When multiple Android builds run in parallel and share the same `ANDROID_HOME`, the Android Gradle Plugin

import org.apache.maven.plugin.InvalidPluginDescriptorException;
import org.apache.maven.plugin.MojoNotFoundException;
import org.apache.maven.plugin.PluginDescriptorParsingException;
import org.apache.maven.plugin.PluginNotFoundException;
import org.apache.maven.plugin.PluginResolutionException;
import org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException;
import org.apache.maven.plugin.version.PluginVersionResolutionException;

  <description>Test that reactor projects are included in dependency resolution.</description>

  <build>
    <outputDirectory>dependency-classes</outputDirectory>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-artifact</artifactId>
        <version>2.1-SNAPSHOT</version>
        <executions>
          <execution>
            <id>compile</id>

 * governing permissions and limitations under the License.
 */
package org.codelibs.fess.app.web.api.admin.plugin;

import org.codelibs.fess.app.web.admin.plugin.DeleteForm;

/**
 * Request body class for plugin deletion API endpoint.
 * Extends the standard plugin DeleteForm to provide JSON request body functionality
 * for REST API operations.
 */
public class DeleteBody extends DeleteForm {