}
                        },
                        "required": True,
                    },
                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {
                                "application/json": {
                                    "schema": {"$ref": "#/components/schemas/BaseUser"}

                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {"application/json": {"schema": {}}},
                        },
                        "422": {
                            "description": "Validation Error",
                            "content": {
                                "application/json": {

                * `description`: A short description of the tag.
                    [CommonMark syntax](https://commonmark.org/) MAY be used for rich
                    text representation.
                * `externalDocs`: Additional external documentation for this tag. If
                    provided, it would contain a `dict` with:
                    * `description`: A short description of the target documentation.

    <artifactId>maven-api</artifactId>
    <version>4.0.0-beta-6-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-cli</artifactId>
  <name>Maven 4 API :: CLI</name>
  <description>Maven 4 API - CLI.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-meta</artifactId>
    </dependency>
    <dependency>

  <version>11-SNAPSHOT</version>
  <name>Model inheritance test parent: module directory != artifactId</name>
  <description>
    artifactId == "child-artifact-id"
    but expect path on SCM and site == "child"
    feature: support "project.directory" property, ressembling future model addition of "directory" element along "artifactId"
  </description>

  <!-- 5 inherited urls with ${project.directory} added to parent instead of artifactId -->

                "put": {
                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {"application/json": {"schema": {}}},
                        },
                        "422": {
                            "description": "Validation Error",
                            "content": {
                                "application/json": {

                    "responses": {
                        "200": {
                            "description": "Successful Response",
                            "content": {"application/json": {"schema": {}}},
                        },
                        "422": {
                            "description": "Validation Error",
                            "content": {
                                "application/json": {

	<modelVersion>4.0.0</modelVersion>
	<artifactId>fess-crawler-lasta</artifactId>
	<packaging>jar</packaging>
	<name>Fess Crawler for LastaFlute</name>
	<description>This is LastaFlute support.</description>
	<parent>
		<groupId>org.codelibs.fess</groupId>
		<artifactId>fess-crawler-parent</artifactId>
		<version>15.0.0-SNAPSHOT</version>
		<relativePath>../pom.xml</relativePath>
	</parent>
	<build>

    <relativePath>../../</relativePath>
  </parent>

  <artifactId>maven-settings-builder</artifactId>

  <name>Maven Settings Builder (deprecated)</name>
  <description>The effective settings builder, with inheritance and password decryption.</description>

  <contributors>
    <contributor>
      <name>Thomas Meyer</name>
    </contributor>
  </contributors>

  <dependencies>
    <dependency>

    <version>26.0-android</version>
  </parent>
  <artifactId>failureaccess</artifactId>
  <version>1.0.2</version>
  <packaging>bundle</packaging>
  <name>Guava InternalFutureFailureAccess and InternalFutures</name>
  <description>
    Contains
    com.google.common.util.concurrent.internal.InternalFutureFailureAccess and
    InternalFutures. Most users will never need to use this artifact. Its