%{snippet|id=jar|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/JarLifecycleMappingProvider.java}

* Plugin bindings for <<<ejb>>> packaging

%{snippet|id=ejb|file=${project.basedir}/src/main/java/org/apache/maven/lifecycle/providers/packaging/EjbLifecycleMappingProvider.java}

* Plugin bindings for <<<maven-plugin>>> packaging

```

</div>

////

The only new option here is `--workers` telling Uvicorn to start 4 worker processes.

You can also see that it shows the **PID** of each process, `27365` for the parent process (this is the **process manager**) and one for each worker process: `27368`, `27369`, `27370`, and `27367`.

## Deployment Concepts { #deployment-concepts }

		<url>scm:git:******@****.***:codelibs/corelib.git</url>
		<developerConnection>scm:git:******@****.***:codelibs/corelib.git</developerConnection>
	  <tag>HEAD</tag>
  </scm>
	<properties>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
	</properties>
	<build>
		<plugins>
			<plugin>
				<artifactId>maven-compiler-plugin</artifactId>
				<version>3.14.0</version>
				<configuration>

        <version>2.1-SNAPSHOT</version>
        <configuration>
          <outputFile>target/expression.properties</outputFile>
          <expressions>
            <expression>project/build/resources/0/filtering</expression>
            <expression>project/repositories</expression>
          </expressions>
        </configuration>
        <executions>
          <execution>
            <id>test</id>
            <phase>validate</phase>

  </parent>

  <groupId>org.apache.maven.validation</groupId>
  <artifactId>project</artifactId>
  <version>1.0.0-SNAPSHOT</version>

  <repositories>
    <repository>
      <id>repo</id>
      <url>file://${basedir}/target/remote-repo</url>
    </repository>
    <repository>
      <id>repo-project-basedir</id>
      <url>file://${project.basedir}/sdk/maven/repo</url>
    </repository>
    <repository>

 * This test specifically verifies the fix for the <a href="https://github.com/apache/maven/pull/2530">issue</a> where
 * getPlugin() was returning disconnected Plugin objects.
 */
class PluginConnectionSimpleTest {

    @Test
    void testPluginModificationPersistsInModel() {
        // Create a test project with a plugin
        Model model = new Model();

        File pom1 = new File(pom0Basedir, "p1/pom.xml");

        // load everything...
        MavenProject project1 = getProjectWithDependencies(pom1);

        assertEquals(pom0Basedir, project1.getParent().getBasedir());
        System.out.println("Project " + project1.getId() + " " + project1);
        Set set = project1.getArtifacts();
        assertNotNull(set, "No artifacts");
        assertFalse(set.isEmpty(), "No Artifacts");

        setPrefix(prefix);

        setRepositorySession(session.getRepositorySession());

        MavenProject project = session.getCurrentProject();
        if (project != null) {
            setRepositories(project.getRemotePluginRepositories());
            setPom(project.getModel());
        }

        setPluginGroups(session.getPluginGroups());
    }

    @Override
    public String getPrefix() {

        In the rare cases where this is infeasible, we will also accept a detailed set of instructions.
        You can also use [Gradle Project Replicator](https://github.com/android/project-replicator) to reproduce the structure of your project.
    validations:
      required: true
  - type: input
    id: gradle-version
    attributes:
      label: Gradle version

     * Registers the specified cache record for usage with the given project. Integrators can use the information
     * collected from this method in combination with a custom cache implementation to dispose unused records from the
     * cache.
     *
     * @param project The project that employs the plugin realm, must not be {@code null}.
     * @param record The cache record being used for the project, must not be {@code null}.
     */