Коли Ви дивитесь автоматичну документацію, Ви можете побачити, що вхідна модель і вихідна модель мають власну JSON-схему:

<img src="/img/tutorial/response-model/image01.png">

І обидві моделі використовуються для інтерактивної API-документації:

<img src="/img/tutorial/response-model/image02.png">

## Інші анотації типів повернення

# Build state model

The Gradle daemon tracks state for various elements. These are arranged in a hierarchy:

```mermaid
  graph TD

  process["build process"]
  
  session["build session"]
  process --> session
  
  build_tree["build tree"]
  session --> build_tree
  
  build1["root build"]
  build_tree --> build1
  
  project1["root project"]
  build1 --> project1
  
  project2["project"]
  build1 --> project2

# Build execution model

At the highest level, Gradle's execution model is quite simple:

Below is the protocol in some more detail:

1. The client looks for a compatible idle daemon. If there isn't one, it starts a new daemon.
2. The client connects to the idle daemon and sends it a request to do some work. If the daemon is no longer running, the client starts again.

org.apache.maven.model.root.DefaultRootLocator...

              <!--              <exclude>org.apache.maven.model.inheritance.DefaultInheritanceAssembler</exclude>-->

    public Model getModel() {
        return model;
    }

    /**
     * Sets the model being wrapped.
     *
     * @param model The model, may be {@code null}.
     */
    public void setModel(Model model) {
        this.model = model;
    }

    /**
     * Gets the raw model being wrapped.
     *
     * @return The raw model or {@code null} if not set.
     */
    public Model getRawModel() {

    /**
     * Gets the file model.
     *
     * @return the file model, never {@code null}.
     */
    @Nonnull
    Model getFileModel();

    /**
     * Gets the file model + build pom transformation, without inheritance nor interpolation.
     *
     * @return The raw model, never {@code null}.
     */
    @Nonnull
    Model getRawModel();

    /**
     * Gets the effective model of the parent POM.
     *

    } // -- void setAddDefaultEntities( boolean )

    protected Model read(Reader reader, boolean strict, InputSource source) throws IOException, XmlPullParserException {
        try {
            org.apache.maven.api.model.Model model =
                    delegate.read(reader, strict, source != null ? source.toApiSource() : null);
            return new Model(model);
        } catch (XMLStreamException e) {

    model: CIBuildModel,
    stage: Stage,
    os: Os? = null,
) = stageTriggerUuid(model, stage.stageName, os)

fun stageTriggerId(
    model: CIBuildModel,
    stageName: StageName,
    os: Os? = null,
) = "${model.projectId}_Stage_${stageName.id}_${osSuffix(os)}Trigger"

fun stageTriggerUuid(
    model: CIBuildModel,
    stageName: StageName,
    os: Os? = null,

import org.apache.maven.api.model.ModelBase;
import org.apache.maven.api.model.Plugin;
import org.apache.maven.api.model.PluginContainer;
import org.apache.maven.api.model.Profile;
import org.apache.maven.api.model.ReportPlugin;
import org.apache.maven.api.model.Reporting;
import org.apache.maven.model.v4.MavenMerger;

/**
 * As long as Maven controls the BuildPomXMLFilter, the entities that need merging are known.