*/
        USER_PROPERTIES,
        /**
         * Project model properties. These properties are defined in the project's POM file (pom.xml) and
         * are read from the project model during the build. They represent build-time configuration that
         * is specific to the project and is stored with the project definition itself rather than in
         * external configuration.
         */
        MODEL

                          Apache Maven

  What is it?
  -----------

  Maven is a software project management and comprehension tool. Based on
  the concept of a Project Object Model (POM), Maven can manage a project's
  build, reporting and documentation from a central piece of information.

  Documentation
  -------------

  The most up-to-date documentation can be found at https://maven.apache.org/.

  Release Notes
  -------------

- The kubernetes repo now uses Go workspaces.  This should not impact end users at all, but does have impact for developers of downstream projects.  Switching to workspaces caused some breaking changes in the flags to the various k8s.io/code-generator tools.  Downstream consumers should look at staging/src/k8s.io/code-generator/kube_codegen.sh to see the changes. ([#123529](https://github....

$ mkdir code
// Gehe in dieses Code-Verzeichnis
$ cd code
// Erstelle ein Verzeichnis für dieses Projekt
$ mkdir awesome-project
// Gehe in dieses Projektverzeichnis
$ cd awesome-project
```

</div>

## Eine virtuelle Umgebung erstellen { #create-a-virtual-environment }

import org.apache.maven.api.model.Profile;
import org.apache.maven.model.building.ModelProblemCollector;
import org.apache.maven.model.profile.ProfileActivationContext;

/**
 * Determines profile activation based on the project's packaging.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Named("packaging")
@Singleton
@Deprecated(since = "4.0.0")

 * Java-related toolchains that can be utilized during the build process
 * in Maven.</p>
 *
 * <p>Java toolchains are defined in the Maven toolchains.xml file and can
 * be referenced in the project's POM file. This enables developers to
 * specify the exact versions of Java tools they wish to use, ensuring
 * consistency across different build environments.</p>
 *
 * @since 4.0.0
 * @see Toolchain

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

import java.io.File;
import java.util.HashMap;
import java.util.Map;

/**
 * Holds all POM files that are known to the reactor. This allows the project builder to resolve imported POMs from the
 * reactor when building another project's effective model.
 */
class ReactorModelPool {

    String UNABLE_TO_FIND_ROOT_PROJECT_MESSAGE = "Unable to find the root directory. "
            + "Create a .mvn directory in the root directory or add the root=\"true\""
            + " attribute on the root project's model to identify it.";

    @Nonnull
    default Path findMandatoryRoot(Path basedir) {
        Path rootDirectory = findRoot(basedir);
        if (rootDirectory == null) {

Vor einiger Zeit fragte <a href="https://github.com/fastapi/fastapi/issues/3#issuecomment-454956920" class="external-link" target="_blank">ein **FastAPI**-Benutzer</a>:

> Was ist die Geschichte dieses Projekts? Es scheint aus dem Nichts in ein paar Wochen zu etwas Großartigem geworden zu sein [...]

Hier ist ein wenig über diese Geschichte.

## Alternativen { #alternatives }

 * <ul>
 *     <li>{@code jar}: Packages the project as a Java Archive (JAR) file.</li>
 *     <li>{@code war}: Packages the project as a Web Application Archive (WAR) file.</li>
 *     <li>{@code pom}: Indicates that the project does not produce a deployable artifact but is used for dependency management or as an aggregator.</li>
 *     <li>{@code maven-plugin}: Packages the project as a Maven plugin.</li>
 * </ul>
 *