<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>

////

/// info

In Pydantic version 1 the method to get the JSON Schema for a model was called `Item.schema()`, in Pydantic version 2, the method is called `Item.model_json_schema()`.

///

Nevertheless, although we are not using the default integrated functionality, we are still using a Pydantic model to manually generate the JSON Schema for the data that we want to receive in YAML.

## Additional Response with `model` { #additional-response-with-model }

You can pass to your *path operation decorators* a parameter `responses`.

It receives a `dict`: the keys are status codes for each response (like `200`), and the values are other `dict`s with the information for each of them.

Each of those response `dict`s can have a key `model`, containing a Pydantic model, just like `response_model`.

import (
	"bytes"
	"context"
	"fmt"
	"reflect"
	"strings"
	"testing"
	"time"

	"gorm.io/gorm"
	"gorm.io/gorm/schema"
	. "gorm.io/gorm/utils/tests"
)

type SerializerStruct struct {
	gorm.Model
	Name                   []byte                 `gorm:"json"`
	Roles                  Roles                  `gorm:"serializer:json"`
	Roles2                 *Roles                 `gorm:"serializer:json"`

  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
  KIND, either express or implied.  See the License for the
  specific language governing permissions and limitations
  under the License.

-->

<model xmlns="http://codehaus-plexus.github.io/MODELLO/2.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://codehaus-plexus.github.io/MODELLO/2.0.0 https://codehaus-plexus.github.io/modello/xsd/modello-2.0.0.xsd"

import common.getBuildScanCustomValueParam
import jetbrains.buildServer.configs.kotlin.BuildSteps
import jetbrains.buildServer.configs.kotlin.buildFeatures.perfmon
import model.CIBuildModel
import model.Stage
import model.StageName
import model.TestCoverage
import model.TestType

const val FUNCTIONAL_TEST_TAG = "FunctionalTest"

sealed class ParallelizationMethod {
    open val extraBuildParameters: String

import jetbrains.buildServer.configs.kotlin.DslContext
import model.CIBuildModel

class PartialTrigger<T : BaseGradleBuildType>(
    triggerName: String,
    triggerId: String,
    model: CIBuildModel,
    dependencies: Iterable<T>,
) : BaseGradleBuildType(init = {
        id("${model.projectId}_${triggerId}_Trigger")
        uuid = "${DslContext.uuidPrefix}_${model.projectId}_${triggerId}_Trigger"
        name = "$triggerName (Trigger)"

 * under the License.
 */
package org.apache.maven.artifact.resolver;

import java.io.File;
import java.util.Collections;
import java.util.List;

import org.apache.maven.model.Model;
import org.apache.maven.model.Repository;
import org.apache.maven.repository.internal.MavenWorkspaceReader;
import org.eclipse.aether.artifact.Artifact;
import org.eclipse.aether.repository.WorkspaceRepository;

import java.nio.file.Path;

import org.apache.maven.api.annotations.Nonnull;
import org.apache.maven.api.annotations.Nullable;

/**
 * Represents a source for loading Maven Project Object Model (POM) files. This interface
 * extends the basic {@link Source} interface with specific functionality for handling
 * Maven POM files and resolving related project POMs.
 *
 * <p>The interface provides two types of sources:</p>

 -----
 Introduction
 -----
 Guillaume Nodet
 -----
 2024-04-04
 -----

Maven 4 API - Repository Metadata Model

 This is the immutable model for Repository Metadata in <<<org.apache.maven.api.metadata>>> package.

 The following are generated from this model: