Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 2 of 2 for structure (0.19 sec)

  1. api/maven-api-toolchain/src/main/mdo/toolchains.mdo

              <type>DOM</type> <!-- DOM for Maven 2.0.9/2.3.3 -->
              <description>
                Toolchain identification information, which will be matched against project requirements.
                &lt;p>Actual content structure is completely open: each toolchain type will define its own format and
                semantics.
                &lt;p>This is generally a properties format: {@code &lt;name&gt;value&lt;/name&gt;} with predefined
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Wed Feb 07 21:28:01 GMT 2024
    - 8.5K bytes
    - Viewed (0)
  2. api/maven-api-model/src/main/mdo/maven.mdo

          </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>
              <code>
                <![CDATA[
        /**
    XML
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Tue Apr 23 13:29:46 GMT 2024
    - 115.1K bytes
    - Viewed (0)
Back to top