<description>The current MavenProject instance, which will have a new executionProject set after execution.</description>
        </parameter>
        <parameter>
          <name>session</name>
          <type>org.apache.maven.execution.MavenSession</type>
          <required>true</required>
          <editable>false</editable>
          <description>The current MavenSession instance, which will handle the fork context.</description>

          <name>goal</name>
          <required>true</required>
          <version>1.0.0+</version>
          <type>String</type>
          <description>
            The goal name for the Mojo, that users will reference from the command line to execute the Mojo directly,
            or inside a POM in order to provide Mojo-specific configuration.
          </description>
        </field>
        <field>

  </parent>

  <groupId>org.apache.maven</groupId>
  <artifactId>maven-bom</artifactId>
  <version>4.0.0-beta-1-SNAPSHOT</version>
  <packaging>pom</packaging>

  <name>Maven Dependencies BOM</name>
  <description>Bill Of Materials for Apache Maven dependencies</description>
  <url>https://maven.apache.org/ref/${project.version}/${project.artifactId}</url>

  <scm>

<dependencies>
  ...
</dependencies>
    ]]></configuration>
    <description>
      <![CDATA[
      This is a set of Artifact instances resolved from the set of dependencies for
      the current project.

      NOTE: This will likely contain much more than the direct dependencies of the
      current POM, since Maven uses transitive, or chained, dependency resolution.
    ]]></description>
  </expression>
  <expression>

    <exportedPackage>javax.inject.*</exportedPackage>
    <!-- javax.enterprise.inject (JSR-299): Must never be exported if needed at plugin level, plugin adds it
         there is no justification to get it at Maven level and leaking it will conflict.
    <exportedPackage>javax.enterprise.util.*</exportedPackage>
    <exportedPackage>javax.enterprise.inject.*</exportedPackage>
    -->

    <!-- javax.annotation (JSR-250) -->

  <!-- localRepository
   | The path to the local repository maven will use to store artifacts.
   |
   | Default: ${user.home}/.m2/repository
  <localRepository>/path/to/local/repo</localRepository>
  -->

  <!-- interactiveMode
   | This will determine whether maven prompts you when it needs input. If set to false,
   | maven will use a sensible default value, perhaps based on some other setting, for

  <inceptionYear>2001</inceptionYear>
  <properties>
    <classWorldsVersion>1.3</classWorldsVersion>
    <commonsCliVersion>1.0</commonsCliVersion>
    <!--

    Do not update this, Doxia will be decoupled completely from 3.x and someone can
    create a rendering engine for it if they like when the release stabilizes. JVZ

    -->
    <doxiaVersion>1.0-alpha-9</doxiaVersion>

        <default-constraints vsize-policy="1" hsize-policy="6" anchor="0" fill="1" />
      </item>
      <item class="com.intellij.uiDesigner.VSpacer" tooltip-text="Vertical Spacer" icon="/com/intellij/uiDesigner/icons/vspacer.png" removable="false" auto-create-binding="false" can-attach-label="false">
        <default-constraints vsize-policy="6" hsize-policy="1" anchor="0" fill="2" />
      </item>

          <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

   |   Based on the toolchain-configuration in the pom.xml Maven will search for
   |   matching <provides/> configuration. You can decide for yourself which key-value
   |   pairs to use. Often used keys are 'version', 'vendor' and 'arch'. By default
   |   the version has a special meaning. If you configured in the pom.xml '1.5'
   |   Maven will search for 1.5 and above.
   |