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,...

          </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>

        return this;
    }

    /**
     * Add the created action message for the key 'errors.login.failure' with parameters.
     * <pre>
     * message: Login failed.
     * comment:
     * /- - - - - - - - - - - - - - - - - - - - - - - - - - - - -
     * five framework-embedded messages (don't change key names)
     * - - - - - - - - - -/
     * </pre>