In order to really achieve this, we need mojo configurations (which are
  provided both in terms of static expressions that are just looked up, and
  in terms of user-provided configuration from properties or the POM).
  If these mojos are to be first-class components, the configuration from these
  various sources must be consolidated and injected using the container.

  Currently, mojo configuration is done externally to the container, in the

            <option value="$PROJECT_DIR$/platforms/core-configuration/configuration-cache-base" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/configuration-problems-base" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/core-flow-services-api" />
            <option value="$PROJECT_DIR$/platforms/core-configuration/core-kotlin-extensions" />

        ProjectBuildingRequest configuration = newBuildingRequest();
        configuration.setRemoteRepositories(Arrays.asList(new ArtifactRepository[] {}));
        configuration.setProcessPlugins(false);
        configuration.setResolveDependencies(true);

        try {
            return projectBuilder.build(pom, configuration).getProject();
        } catch (Exception e) {

    <url>scp://host/path/to/repo</url>
  </snapshotRepository>
</distributionManagement>
    ]]></configuration>
    <description> This is the ArtifactRepository used to deploy artifacts built by this
      Maven.
    </description>
  </expression>
  <expression>
    <syntax>project.artifact</syntax>
    <configuration>
      <![CDATA[
<groupId>project.group</groupId>
<artifactId>project-artifact</artifactId>

Um Tags zu Ihren *Pfadoperationen* hinzuzufügen und diese in der Oberfläche der Dokumentation zu gruppieren, lesen Sie die Dokumentation unter [Tutorial – Pfadoperation-Konfiguration – Tags](../tutorial/path-operation-configuration.md#tags){.internal-link target=_blank}.

## Zusammenfassung und Beschreibung in der Dokumentation – OpenAPI { #documentation-summary-and-description-openapi }

    "crossVersionTests": false
  },
  {
    "name": "configuration-cache",
    "path": "platforms/core-configuration/configuration-cache",
    "unitTests": true,
    "functionalTests": true,
    "crossVersionTests": true
  },
  {
    "name": "configuration-cache-base",
    "path": "platforms/core-configuration/configuration-cache-base",
    "unitTests": false,
    "functionalTests": false,

That configuration would change the syntax highlighting color theme:

<img src="/img/tutorial/extending-openapi/image04.png">

## Change Default Swagger UI Parameters { #change-default-swagger-ui-parameters }

FastAPI includes some default configuration parameters appropriate for most of the use cases.

It includes these default configurations:

            <goals>
              <goal>unpack-dependencies</goal>
            </goals>
            <configuration>
              <includeArtifactIds>jline-native</includeArtifactIds>
              <includes>org/jline/nativ/**</includes>
            </configuration>
          </execution>
        </executions>
      </plugin>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>

    } // -- void removeExecution( Execution )

    /**
     * Set configuration to pass to all goals run in this phase.
     *
     * @param configuration a configuration object.
     */
    public void setConfiguration(Object configuration) {
        this.configuration = configuration;
    } // -- void setConfiguration( Object )

    /**
     * Set the goals to execute within the phase.

  - Bucket Tags
  - Bucket Object-Lock configurations (including retention and legal hold configuration)
  - Bucket Encryption configuration

> NOTE: Bucket versioning is automatically enabled for all new and existing buckets on all replicated sites.

The following Bucket features will **not be replicated**, is designed to differ between sites:

- Bucket notification configuration
- Bucket lifecycle (ILM) configuration