Priority for profiles activated by property or -P unclear

I could not find the situation documented somewhere, but the current behaviour is against my excpectation, hence a low priority bug report. In my pom, I have two profiles. One is activated by the -P command line option, the other by an environment variable. In variation of the example in MNG-2309:

<profile>
  <id>default</id>
  <activation>
    <property>
      <name>env.WORKSPACE</name>
    </property>
  </activation>
  <properties>
    <test>DEFAULT</test>
  </properties>
</profile>

<profile>
  <id>override</id>
  <properties>
    <test>OVERRIDE</test>
  </properties>
</profile>

env.WORKSPACE is set by Hudson, when the build is executed. When Hudson runs "mvn -P override" I would expect test set to override. As I said, this is my expectation, and I don't know if it was a consious design decision to make the priority of profile activation differently.