title: is it possible to "extend" a profile in a child module?
body: <p>say i have a parent pom A, with profiles win32 and win64 activated by os:</p>
  
  <pre><code>&lt;profile&gt;
      &lt;id&gt;windows32&lt;/id&gt;
      &lt;activation&gt;
          &lt;os&gt;
              &lt;family&gt;windows&lt;/family&gt;
              &lt;arch&gt;x86&lt;/arch&gt;
          &lt;/os&gt;
      &lt;/activation&gt;
      &lt;properties&gt;
          &lt;envClassifier&gt;win-x32&lt;/envClassifier&gt;
      &lt;/properties&gt;
  &lt;/profile&gt;
  &lt;profile&gt;
      &lt;id&gt;windows64&lt;/id&gt;
      &lt;activation&gt;
          &lt;os&gt;
              &lt;family&gt;windows&lt;/family&gt;
              &lt;arch&gt;amd64&lt;/arch&gt;
          &lt;/os&gt;
      &lt;/activation&gt;
      &lt;properties&gt;
          &lt;envClassifier&gt;win-x64&lt;/envClassifier&gt;
      &lt;/properties&gt;
  &lt;/profile&gt;
  </code></pre>
  
  <p>those profiles define env. variables like ${envClassifier} etc.
  say that parent module has a child module B which would like to define some extra stuff IN ADDITION on win64:</p>
  
  <pre><code>&lt;profile&gt;
      &lt;id&gt;windows64&lt;/id&gt;
      &lt;properties&gt;
          &lt;jreName&gt;jre6u27.zip&lt;/jreName&gt;
      &lt;/properties&gt;
  &lt;/profile&gt;
  </code></pre>
  
  <p>can i somehow extend the win64 profile from the parent, or am i doomed to copy-and-paste it along with its activation section and everything?</p>