-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <groupId>org.apache.maven.its.mng</groupId>
  <artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <!-- minimal parent just to have one more level of inheritance -->

    <version>1</version>
  </parent>

  <groupId>org.apache.maven.validation</groupId>
  <artifactId>project</artifactId>
  <version>1.0.0-SNAPSHOT</version>

  <properties>
    <x>just/some/path</x>
  </properties>

  <repositories>
    <repository>
      <id>repo</id>
      <url>file://${x}/sdk/maven/repo</url>
    </repository>
  </repositories>

          <version>4.0.0+</version>
          <description>
            <![CDATA[
            Just like {@code connection}, but for developers, i.e. this scm connection
            will not be read only.
            <p><b>Default value is</b>: parent value [+ path adjustment] + (artifactId or project.directory property), or just parent value if
            scm's {@code child.scm.developerConnection.inherit.append.path="false"}.</p>

    classes are conceptually a part of Guava, but they're in this separate
    artifact so that Android libraries can use them without pulling in all of
    Guava (just as they can use ListenableFuture by depending on the
    listenablefuture artifact).
  </description>
  <build>
    <plugins>
      <plugin>
        <artifactId>maven-jar-plugin</artifactId>
        <configuration>

0x1.5e-2     // invalid: hexadecimal mantissa requires p exponent
1_.5         // invalid: _ must separate successive digits
1._5         // invalid: _ must separate successive digits
1.5_e1       // invalid: _ must separate successive digits
1.5e_1       // invalid: _ must separate successive digits
1.5e1_       // invalid: _ must separate successive digits
</pre>


<h3 id="Imaginary_literals">Imaginary literals</h3>

function contains no call instructions.
Otherwise, the local stack frame must not contain pointers,
and the assembly must confirm this fact by executing the
pseudo-instruction <code>NO_LOCAL_POINTERS</code>.
Because stack resizing is implemented by moving the stack,
the stack pointer may change during any function call:
even pointers to stack data must not be kept in local variables.
</p>

<p>

     |     <tomcatLocation>${tomcatPath}</tomcatLocation>
     |   </configuration>
     | </plugin>
     | ...
     |
     | NOTE: If you just wanted to inject this configuration whenever someone set 'target-env' to
     |       anything, you could just leave off the <value/> inside the activation-property.
     |
    <profile>
      <id>env-dev</id>

      <activation>
        <property>

<project>
  <modelVersion>4.0.0</modelVersion>
  <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>

<project>
  <modelVersion>4.0.0</modelVersion>
  <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>

      <releases>
        <enabled>false</enabled>
      </releases>
    </repository>
  </repositories>
  <distributionManagement>
    <!-- Site omitted - each project must provide their own -->
    <repository>
      <id>apache.releases</id>
      <name>Apache Release Distribution Repository</name>
      <url>scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</url>