<name>configuration</name>
          <description>The place and syntax used to change the value of this expression.</description>
          <type>String</type>
        </field>
        <field>
          <version>1.0.0</version>
          <name>cliOptions</name>
          <description>The command-line switches used to change the value of this expression.</description>
          <type>Properties</type>

  <version>
    1.0
  </version>
  <packaging>
    pom
  </packaging>

  <name>Maven Integration Test :: MNG-4070</name>
  <description>
    Test that whitespace around artifact coordinates does not change artifact identity.
  </description>

  <version>1.0</version>
  <packaging>jar</packaging>

  <name>Maven Integration Test :: MNG-4070 :: Child</name>
  <description>
    Test that whitespace around artifact coordinates does not change artifact identity.
  </description>

  <dependencies>
    <dependency>
      <!-- NOTE: The ugly formatting is essential part of this test! -->
      <groupId>   org.apache.maven.its.mng4070   </groupId>

  |   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)
  |
  | o annotation mechanism so that changes to the model can be accurately tracked.
  |
  | o need to clean up all the descriptions, matching anything to the current project-descriptor.xml file and
  |   improving on that
  |

              <include>org.apache.maven.toolchain</include>
              <include>org.apache.maven.usability</include>
            </includes>
            <!-- allowed non-binary backwards compatible changes -->
            <excludes>
              <!-- START default constructor on Plexus/JSR 330 components -->
              <exclude>org.apache.maven.lifecycle.DefaultLifecycleExecutor#DefaultLifecycleExecutor()</exclude>

            define its own format and semantics. This was generally a properties format.
            <p>Since Maven 3.2.4, the type for this field has been changed to Properties to match the de-facto
            format.
            <p>Each toolchain defines its own properties names and semantics.
          </description>
        </field>
        <field>

                changed = true;
            }
        }

        Versioning versioning = sourceMetadata.getVersioning();
        if ( versioning != null )
        {
            Versioning v = getVersioning();
            if ( v == null )
            {
                v = new Versioning();
                setVersioning( v );
                changed = true;
            }

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>parent-version-range-local</groupId>
  <artifactId>parent</artifactId>
  <version>1</version>
  <packaging>pom</packaging>

  <parent>
    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>[1,1]</version>
  </parent>
  <artifactId>child</artifactId>
  <!-- Must not use ${project.version} due to version range. -->
  <version>${project.version}</version>
  <packaging>pom</packaging>

    <groupId>org.apache</groupId>
    <artifactId>apache</artifactId>
    <version>[1,1]</version>
  </parent>
  <artifactId>child</artifactId>
  <!-- version>2</version Must not inherit version from parent due to version range. -->
  <packaging>pom</packaging>