// configuration. We don't have an easy way to allow a pluggable builder to provide its own configuration
        // parameters but this is sufficient for now. Ultimately we want components like Builders to provide a way to
        // extend the command line to accept its own configuration parameters.
        //

        };
    }

    protected LoggerManager createLoggerManager() {
        return new Slf4jLoggerManager();
    }

    protected void customizeContainerConfiguration(C context, ContainerConfiguration configuration) throws Exception {}

    protected void customizeContainer(C context, PlexusContainer container) throws Exception {}

    protected List<Path> parseExtClasspath(C context) throws Exception {

### 自作タグの使用

`tags` パラメーターを使用して、それぞれの *path operations* (および `APIRouter`) を異なるタグに割り当てます:

{* ../../docs_src/metadata/tutorial004.py hl[21,26] *}

/// info | 情報

タグのより詳しい説明を知りたい場合は [Path Operation Configuration](path-operation-configuration.md#tags){.internal-link target=_blank} を参照して下さい。

///

### ドキュメントの確認

ここで、ドキュメントを確認すると、追加したメタデータがすべて表示されます:

<img src="/img/tutorial/metadata/image02.png">

### タグの順番

	xioutil "github.com/minio/minio/internal/ioutil"
)

func defaultFilenameFunc() string {
	return fmt.Sprintf("minio-%s.log", fmt.Sprintf("%X", time.Now().UTC().UnixNano()))
}

// Options define configuration options for Writer
type Options struct {
	// Directory defines the directory where log files will be written to.
	// If the directory does not exist, it will be created.
	Directory string

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Installing the Chart (toy-setup) Minimal toy setup for testing purposes can be deployed using: ```bash helm install --set resources.requests.memory=512Mi...

Installing the Chart Install this chart using: ```bash helm install --namespace minio --set rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. ### Upgrading the Chart You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using...

import org.apache.maven.model.building.ModelBuildingRequest;
import org.apache.maven.model.building.ModelProblemCollector;
import org.codehaus.plexus.util.xml.Xpp3Dom;

/**
 * Handles expansion of general build plugin configuration into individual executions.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Named
@Singleton
@Deprecated(since = "4.0.0")

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

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

/**
 * Factory interface for creating new RequestCache instances.
 * Implementations should handle the creation and configuration of cache instances
 * based on the current Maven session and environment.
 *
 * @since 4.0.0
 * @see RequestCache
 */
@Experimental
public interface RequestCacheFactory {

    /**

            context.terminal
                    .writer()
                    .println(
                            "Note: Generated configuration can be moved/copied to headless environments, if configured as such.");
            return EncryptInvoker.BAD_OPERATION;
        }

        return doExecute(context);
    }

  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.lifecycle.test</groupId>
  <artifactId>mojo-configuration</artifactId>
  <packaging>jar</packaging>
  <version>1.0</version>
  <name>project-with-additional-lifecycle-elements</name>
  <url>http://maven.apache.org</url>

  <build>
    <pluginManagement>
      <plugins>