<modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng4341</groupId>
  <artifactId>test</artifactId>
  <version>0.1</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4341</name>
  <description>

    <version>1.0-SNAPSHOT</version>
  </parent>

  <artifactId>child-project</artifactId>
  <version>1.0-SNAPSHOT</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.its.plugins</groupId>
        <artifactId>maven-it-plugin-log-file</artifactId>

            <multiplicity>*</multiplicity>
          </association>
        </field>
      </fields>
      <codeSegments>
        <codeSegment>
          <version>1.0.0</version>
          <code><![CDATA[    private java.util.Map expressionsBySyntax;

    public java.util.Map getExpressionsBySyntax()
    {
        if ( expressionsBySyntax == null )
        {

    ]]></configuration>
      <description>
        <![CDATA[
      Flags the system as offline, to prevent accessing the network to resolve artifacts or execute plugins.

      NOTE: It's also possible to switch to offline mode on a per-build basis, using the '-o' command-line option.
    ]]></description>
    </expression>
    <expression>
      <syntax>settings.interactiveMode</syntax>
      <configuration>
        <![CDATA[

  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng4332</groupId>
  <artifactId>test</artifactId>
  <version>0.1</version>
  <!-- NOTE: The upper-case packaging name is intentional and triggers a special mode in the EmptyLifecycleExecutor -->
  <packaging>JAR</packaging>

  <name>Maven Integration Test :: MNG-4332</name>
  <description>

  <id>extension</id>
  <name>ExtensionDescriptor</name>
  <description><![CDATA[
    Extension descriptor, stored in <code>META-INF/maven/extension.xml</code> in an extension's jar artifact to
    precisely control parts of the extension and dependencies to expose in the API class loader.

    {@code META-INF/maven/lifecycle.xml} in a plugin's jar artifact.
  </description>
  <classes>
    <class rootElement="true" xml.tagName="lifecycles" xsd.compositor="sequence">
      <name>LifecycleConfiguration</name>
      <version>1.0.0</version>
      <description>Root element of the {@code lifecycle.xml} file.</description>
      <fields>
        <field>

    if match is found, the toolchain instance is made available to other Maven plugins.</p>
    <p>With {@code jdk} toolchain, for example, instead of being stuck with the JDK used to run Maven, all plugins can use
    the same other JDK instance without hardcoding absolute paths into the {@code pom.xml}