|
  | o validators: there could be several levels of validation. Simple type validation could
  |   be done with a regex, but we need inter-field validation and rules which could be
  |   dealt with by something like drools.
  |
  | o i18n: would be good to be able to have names/descriptions/specifications
  |   in as many languages as possible. (see MNG-3626)
  |

        </field>
        <field>
          <name>configuration</name>
          <version>1.0.0+</version>
          <type>DOM</type>
          <description>
            Toolchain configuration information, like location or any information that is to be retrieved.
            &lt;p>Actual content structure is completely open: each toolchain type will define its own format and
            semantics.

    <p>This is a reference for the user-specific configuration for Maven.</p>
    <p>Includes things that should not be distributed with the <code>pom.xml</code> file, such as developer identity, along with
    local settings, like proxy information.</p>
    <p>The default location for the settings file is {@code ~/.m2/settings.xml}.</p>
    ]]>
  </description>
  <defaults>
    <default>
      <key>package</key>