<type>String</type>
            <multiplicity>*</multiplicity>
          </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>

method on that type, passing the the examined object. The created matcher forces a relationship between specified type and the examined object, and should be used when it is necessary to make generics conform, for example in the JMock clause with(any(Thing.class)) For example: assertThat(new Canoe(), instanceOf(Canoe.class)); instanceOf public static <T> Matcher<T> instanceOf(java.lang.Class<?> type) Creates a matcher that matches when the examined object is an instance of the specified type, as determined...