</goals>
            <configuration>
              <version>1.1.0</version>
              <models>
                <model>src/main/mdo/remote-resources.mdo</model>
              </models>
            </configuration>
          </execution>
          <execution>
            <id>supplemental-models</id>
            <goals>
              <goal>xpp3-writer</goal>
              <goal>java</goal>

It's **not supported** by Pydantic to have a model of Pydantic v2 with its own fields defined as Pydantic v1 models or vice versa.

```mermaid
graph TB
    subgraph "❌ Not Supported"
        direction TB
        subgraph V2["Pydantic v2 Model"]
            V1Field["Pydantic v1 Model"]
        end
        subgraph V1["Pydantic v1 Model"]
            V2Field["Pydantic v2 Model"]
        end
    end

Sebastián Ramírez <******@****.***> 1731896744 +0100

timothy <******@****.***> 1748612313 +0900

            </goals>
            <configuration>
              <version>1.1.0</version>
              <models>
                <model>../../api/maven-api-metadata/src/main/mdo/metadata.mdo</model>
              </models>
              <templates>
                <template>model-v3.vm</template>
              </templates>
            </configuration>
          </execution>
        </executions>
      </plugin>

### Model for Input { #model-for-input }

If you use this model as an input like here:

{* ../../docs_src/separate_openapi_schemas/tutorial001_py310.py ln[1:15] hl[14] *}

...then the `description` field will **not be required**. Because it has a default value of `None`.

### Input Model in Docs { #input-model-in-docs }

     */
    List<String> getModelIds();

    /**
     * Gets the assembled model.
     *
     * @return The assembled model, never {@code null}.
     */
    Model getEffectiveModel();

    /**
     * Gets the raw model as it was read from the input model source. Apart from basic validation, the raw model has not

              <goal>velocity</goal>
            </goals>
            <configuration>
              <version>4.0.0</version>
              <models>
                <model>target/mdo/maven.mdo</model>
              </models>
              <templates>
                <template>src/main/mdo/model-v3.vm</template>
                <template>src/main/mdo/merger.vm</template>
                <template>src/main/mdo/transformer.vm</template>

 * The maven super model

 * how parent poms are processed

 * the order in which elements in the POM are overridden

 * minimum element-set for a valid project pom


Maven super model

 Inheritance is recursive in Maven but there is a special model which is the implicit super parent in the lineage
 of models you may specify:

          <velocityBasedir>${project.basedir}/../../src/mdo</velocityBasedir>
          <models>
            <model>src/main/mdo/maven.mdo</model>
          </models>
          <templates>
            <template>model.vm</template>
          </templates>
          <params>
            <param>packageModelV4=org.apache.maven.api.model</param>
            <param>isMavenModel=true</param>
            <param>locationTracking=true</param>