</association>
        </field>
      </fields>
      <comment>We could probably have a specific element for a dev mailing list for things like CI,
        and maybe even a specific element for the user and scm mailing lists. Then leave the more
        lose structure for any other type of mailing list.</comment>
      <codeSegments>
        <codeSegment>
          <version>4.0.0+</version>

XmlSerializer text(char[], int, int) throws java.io.IOException; public void cdsect(String) throws java.io.IOException; public void entityRef(String) throws java.io.IOException; public void processingInstructio(String) throws java.io.IOException; public void comment(String) throws java.io.IOException; public void docdecl(String) throws java.io.IOException; public void ignorableWhitespace(String) throws java.io.IOException; public void flush() throws java.io.IOException; protected void writeAttributeValue(String,...

      <name>Plugin</name>
      <version>1.0.0+</version>
      <description>Mapping information for a single plugin within this group.</description>
      <comment>NOTE: plugin version is _NOT_ included here, since it is resolved using a separate algorithm in plugins' artifact.</comment>
      <fields>
        <field>
          <name>name</name>
          <type>String</type>
          <required>true</required>