title: How to keep Maven profiles which are activeByDefault active even if another profile gets activated?
body: <p>I have a profile in my pom.xml which should be always active unless it is explicitely deactivated (-P !firstProfile).
  I solved this by using the activeByDefault flag:</p>
  
  <pre><code>&lt;profiles&gt;
    &lt;profile&gt;
      &lt;id&gt;firstProfile&lt;/id&gt;
      &lt;activation&gt;
        &lt;activeByDefault&gt;true&lt;/activeByDefault&gt;
      &lt;/activation&gt;
      ...
    &lt;/profile&gt;
  &lt;/profiles&gt;
  </code></pre>
  
  <p>Now in the same pom.xml I have a second profile defined this should only be active if the profile is really activated (-P secondProfile).
  So the default behaviour is: firstProfile active, secondProfile inactive.
  At some other point I would like to activated the second profile in addition to the first profile.
  Now the problem is that if I do that with "-P secondProfile" the firstProfile unfortunately gets deactivated.
  The Maven documentation states this:</p>
  
  <blockquote>
    <p>... 
    This profile will automatically be
    active for all builds unless another
    profile in the same POM is activated
    using one of the previously described
    methods. All profiles that are active
    by default are automatically
    deactivated when a profile in the POM
    is activated on the command line or
    through its activation config. 
    ...</p>
  </blockquote>
  
  <p>Is there somehow a possibility how to keep the firstProfile always active (without having to declare it in the settings.xml)?</p>