<artifactId>parent</artifactId>
  <version>0.1</version>
  <packaging>pom</packaging>

  <name>Maven Integration Test :: MNG-4415</name>
  <description>
    Test that merging of plugins during inheritance follows these rules regarding ordering:
     parent: X ->      A -> B ->      D -> E
     child:       Y -> A ->      C -> D ->      F
     result: X -> Y -> A -> B -> C -> D -> E -> F
  </description>

  <build>

  <artifactId>test</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4415</name>
  <description>
    Test that merging of plugins during inheritance follows these rules regarding ordering:
     parent: X ->      A -> B ->      D -> E
     child:       Y -> A ->      C -> D ->      F
     result: X -> Y -> A -> B -> C -> D -> E -> F
  </description>

  <build>

  <artifactId>test</artifactId>
  <version>0.1</version>

  <name>Maven Integration Test :: MNG-4416</name>
  <description>
    Test that merging of plugins during profile injection follows these rules regarding ordering:
     model:   X ->      A -> B ->      D -> E
     profile:      Y -> A ->      C -> D ->      F
     result:  X -> Y -> A -> B -> C -> D -> E -> F
  </description>

  <build>

            Other values define only the prefix of classes/resources being exposed. Their binary name must be equal to the prefix or starting with the prefix (followed by "." or "$").
            In particular this includes all subpackages. Despite the element name one can also only expose individual classes of a particular package by adding its binary name as value.
          ]]></description>