specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!--
  This minimalist POM tests mere inheritance from its parent. The <prerequisites> should not be inherited.
  -->

  <parent>
    <groupId>org.apache.maven.its.mng3843</groupId>
    <artifactId>parent-1</artifactId>
    <version>0.1</version>

            <p><b>Note:</b> This will not automagically make a Mojo run when the plugin declaration is added
            to the POM. It merely enables the user to omit the {@code <phase>} element from the
            surrounding {@code <execution>} element.</p>
          </description>
        </field>
        <field>

specific language governing permissions and limitations
under the License.
-->

<project>
  <modelVersion>4.0.0</modelVersion>

  <!--
  This minimalist POM tests mere inheritance from its parent.
  -->

  <parent>
    <groupId>org.apache.maven.its.mng3843</groupId>
    <artifactId>parent-1</artifactId>
    <version>0.1</version>
  </parent>

   | section of this document (settings.xml) - will be discussed later. Another way essentially
   | relies on the detection of a property, either matching a particular value for the property,
   | or merely testing its existence. Profiles can also be activated by JDK version prefix, where a
   | value of '1.4' might activate a profile when the build is executed on a JDK version of '1.4.2_07'.