</field>
      </fields>
    </class>

    <class xdoc.anchorName="dependency">
      <name>Dependency</name>
      <version>1.0.0/1.1.0</version>
      <description>Definition of a dependency, needed by the plugin at runtime.</description>
      <fields>
        <field>
          <name>groupId</name>
          <required>true</required>
          <version>1.0.0+</version>
          <type>String</type>

          <description>A detailed description of the project, used by Maven whenever it needs to
            describe the project, such as on the website. While this element can be specified as
            CDATA to enable the use of HTML tags within the description, it is discouraged to allow
            plain text representation. If you need to modify the index page of the generated website,

    <!--
      | We may potentially want to export these, but right now I'm not sure that anything Guice specific needs
      | 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.

    <class java.clone="deep">
      <name>RepositoryBase</name>
      <version>1.0.0+</version>
      <superClass>IdentifiableBase</superClass>
      <description>
        Repository contains the information needed
        for establishing connections with remote repository
      </description>
      <fields>
        <field>
          <name>name</name>
          <version>1.0.0+</version>
          <description>