|
   | As noted above, profiles can be activated in a variety of ways. One way - the activeProfiles
   | 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

  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3916</name>
  <description>
    Test that plugin executions are properly merged during inheritance, even if the child plugin section has no
    version.
  </description>

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

  <name>Maven Integration Test :: MNG-2174</name>
  <description>
    Verify that plugin dependencies defined by plugin management of a parent profile are not lost when the
    parent's main plugin management section is also present.
  </description>

  <modules>
    <module>sub</module>
  </modules>

  <build>
    <pluginManagement>
      <plugins>
        <plugin>

            mobile platform, to enable easy switching of entire proxy
            configurations by simply specifying the profile id, again either from
            the command line or from the defaults section below.
          </description>
          <association>
            <type>Proxy</type>
            <multiplicity>*</multiplicity>
          </association>
        </field>
        <field xdoc.separator="blank">

      <w>pparent</w>
      <w>precheck</w>
      <w>prioritizer</w>
      <w>processings</w>
      <w>rbrace</w>
      <w>rbracket</w>
      <w>renderers</w>
      <w>rparenth</w>
      <w>selectioner</w>
      <w>smartcast</w>
      <w>summand</w>
      <w>unpluralize</w>
      <w>weighers</w>
    </words>
  </dictionary>