<jsp:param name="menuCategoryType" value="user"/>
        <jsp:param name="menuType" value="group"/>
    </jsp:include>
    <main class="content-wrapper">
        <div class="content-header">
            <div class="container-fluid">
                <div class="row mb-2">
                    <div class="col-sm-6">
                        <h1>
                            <la:message key="labels.group_title_details"/>
                        </h1>

 * annotation.  If a {@code META-INF/maven/lifecycle.xml} file is packaged
 * in the plugin, Maven will provide a default implementation that will parse
 * the file and return the contained lifecycle definitions.
 *
 * @since 4.0.0
 */
@Experimental
@Consumer
public interface LifecycleProvider {

    List<Lifecycle> getLifecycles();

			<jsp:param name="menuCategoryType" value="system" />
			<jsp:param name="menuType" value="sereq" />
		</jsp:include>
		<main class="content-wrapper">
			<div class="content-header">
				<div class="container-fluid">
					<div class="row mb-2">
						<div class="col-sm-6">
							<h1>
								<la:message key="labels.sereq_configuration" />
							</h1>
						</div>
					</div>
				</div>
			</div>

/**
 * A utility class to assist in setting up a Maven-like repository system. Note: This component is meant to
 * assist those clients that employ the repository system outside of an IoC container, Maven plugins should instead
 * always use regular dependency injection to acquire the repository system.
 *
 * @deprecated See {@link MavenSessionBuilderSupplier}
 */
@Deprecated

/**
 * Marks a method as a provider of beans for dependency injection.
 * <p>
 * This annotation can be used on static methods to programmatically create and configure
 * beans that will be managed by the dependency injection container. It's particularly
 * useful when the bean creation requires complex logic or when the bean needs to be
 * configured based on runtime conditions.
 * <p>
 * Example usage:
 * <pre>
 * public class Providers {

 * system. Custom scope annotations should be annotated with {@code @Scope}.
 * <p>
 * Built-in scopes include:
 * <ul>
 *   <li>{@link Singleton} - One instance per container</li>
 *   <li>{@link SessionScoped} - One instance per Maven session</li>
 *   <li>{@link MojoExecutionScoped} - One instance per plugin execution</li>
 * </ul>
 *
 * @see Singleton
 * @see SessionScoped

     *            be <code>null</code>.
     * @param request The model building request that holds further settings, must not be {@code null}.
     * @param problems The container used to collect problems that were encountered, must not be {@code null}.
     */
    void injectManagement(Model model, ModelBuildingRequest request, ModelProblemCollector problems);

     *            <code>null</code>.
     * @param request The model building request that holds further settings, must not be {@code null}.
     * @param problems The container used to collect problems that were encountered, must not be {@code null}.
     */
    void injectManagement(Model model, ModelBuildingRequest request, ModelProblemCollector problems);

{* ../../docs_src/request_forms_and_files/tutorial001_an_py310.py hl[10:12] *}

Les fichiers et les champs de formulaire seront téléversés en tant que données de formulaire et vous les recevrez.

Et vous pouvez déclarer certains fichiers comme `bytes` et d'autres comme `UploadFile`.

/// warning | Alertes

## Monitoring MinIO in Kubernetes

MinIO server exposes un-authenticated liveness endpoints so Kubernetes can natively identify unhealthy MinIO containers. MinIO also exposes Prometheus compatible data on a different endpoint to enable Prometheus users to natively monitor their MinIO deployments.

## Explore Further