<configuration>
          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <version>1.2.0</version>
          <models>
            <model>src/main/mdo/metadata.mdo</model>
          </models>
          <templates>
            <template>model.vm</template>
          </templates>
          <params>
            <param>packageModelV4=org.apache.maven.api.metadata</param>
          </params>

## Other models { #other-models }

You can now get the current user directly in the *path operation functions* and deal with the security mechanisms at the **Dependency Injection** level, using `Depends`.

And you can use any model or data for the security requirements (in this case, a Pydantic model `User`).

But you are not restricted to using some specific data model, class or type.

        <artifactId>modello-maven-plugin</artifactId>
        <version>1.0.1</version>
        <configuration>
          <version>1.1.0</version>
          <models>
            <model>src/main/mdo/remote-resources.mdo</model>
          </models>
        </configuration>
      </plugin>
    </plugins>
  </build>

        <artifactId>modello-maven-plugin</artifactId>
        <configuration>
          <version>1.2.0</version>
          <models>
            <model>src/main/mdo/core-extensions.mdo</model>
          </models>
          <templates>
            <template>model.vm</template>
          </templates>
          <params>
            <param>locationTracking=true</param>

          <basedir>${project.basedir}/../../api/maven-api-toolchain</basedir>
          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <models>
            <model>src/main/mdo/toolchains.mdo</model>
          </models>
        </configuration>
        <executions>
          <execution>
            <id>velocity</id>
            <goals>
              <goal>velocity</goal>
            </goals>

## Use Case { #use-case }

Let's start with an example **use case** and then see how to solve it with this.

Let's imagine that you have some **machine learning models** that you want to use to handle requests. 🤖

The same models are shared among requests, so, it's not one model per request, or one per user or something similar.

 * under the License.
 */
package org.apache.maven.model.normalization;

import org.apache.maven.model.Model;
import org.apache.maven.model.building.ModelBuildingRequest;
import org.apache.maven.model.building.ModelProblemCollector;

/**
 * Handles normalization of a model. In this context, normalization is the process of producing a canonical
 * representation for models that physically look different but are semantically equivalent.
 *

          <basedir>${project.basedir}/../../api/maven-api-model</basedir>
          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <version>4.1.0</version>
          <models>
            <model>src/main/mdo/maven.mdo</model>
          </models>
          <params>
            <param>forcedIOModelVersion=4.0.0</param>
            <param>packageModelV3=org.apache.maven.model</param>

 */
package org.apache.maven.model.superpom;

import org.apache.maven.model.Model;

/**
 * Provides the super POM that all models implicitly inherit from.
 *
 * @deprecated use {@code org.apache.maven.api.services.ModelBuilder} instead
 */
@Deprecated(since = "4.0.0")
public interface SuperPomProvider {

    /**

 */
package org.apache.maven.model.composition;

import javax.inject.Named;
import javax.inject.Singleton;

import java.util.ArrayList;
import java.util.LinkedHashMap;
import java.util.List;
import java.util.Map;

import org.apache.maven.model.Dependency;
import org.apache.maven.model.DependencyManagement;
import org.apache.maven.model.Model;
import org.apache.maven.model.building.ModelBuildingRequest;