<field xml.tagName="field-name">
          <name>fieldName</name>
          <required>true</required>
          <version>1.0.0+</version>
          <type>String</type>
          <description>The field name which has this requirement.</description>
        </field>
      </fields>
    </class>

    <class xdoc.anchorName="dependency">
      <name>Dependency</name>
      <version>1.0.0/1.1.0</version>

          i.e. referencing any of those coordinates in plugin/build extension dependencies has no effect.]]>
          </description>
        </field>
      </fields>
    </class>
  </classes>

      <version>4.0.0+</version>
      <description>Describes where an artifact has moved to. If any of the values are omitted, it is
        assumed to be the same as it was before.</description>
      <fields>
        <field>
          <name>groupId</name>
          <version>4.0.0+</version>
          <description>The group ID the artifact has moved to.</description>
          <type>String</type>
        </field>

      | to be made available to plugin authors. If we find people are getting fancy and want to take advantage of
      | Guice specifics we can expose that later. Really some testing needs to be done to see full hiding
      | of Guice has any impact on what we may categorize as a standard JSR-330 based Tesla/Maven plugin.

        <exportedPackage>com.google.inject.*</exportedPackage>
        <exportedPackage>com.google.inject.binder.*</exportedPackage>

              <!-- internal field removed -->
              <exclude>org.apache.maven.graph.DefaultGraphBuilder#projectBuilder</exclude>
              <!-- MavenPluginValidator has been transformed into an interface -->
              <exclude>org.apache.maven.plugin.MavenPluginValidator</exclude>
              <!-- Remove plexus logger -->

            define its own format and semantics. This was generally a properties format.
            <p>Since Maven 3.2.4, the type for this field has been changed to Properties to match the de-facto
            format.
            <p>Each toolchain defines its own properties names and semantics.
          </description>
        </field>
        <field>

    <p>Per-directory repository metadata <code>repository-metadata.xml</code>.</p>
    <p>A directory may represent 3 types of content: "groupId", "groupId/artifactId" or "groupId/artifactId/version".</p>
    <p>Most metadata content has a meaning when the directory represents a "groupId/artifactId" (<code>groupId</code>, <code>artifactId</code>, <code>versioning</code>)<p>]]>
  </description>
  <defaults>
    <default>
      <key>package</key>