[MNG-8081] default profile activation should consider available system and user properties

[jira-importer]

Matthew Jason Benson opened MNG-8081 and commented

As discussed in my open PR, my use case is to compare between environment variables e.g.:

<activation>
  <property>
    <name>env.FOO</name>
    <value>${env.BAR}</value>
  </property>
</activation>

Limiting the interpolation to user/system properties means that there is no mindf*ck resulting from profile activation order, etc., and keeps this request nonthreatening.

---

Affects: 3.9.6, 4.0.0

Issue Links:

• MNG-5235 Profiles not activated according to property values

Remote Links:

• GitHub Pull Request #1446
  
• GitHub Pull Request #1447
  
• GitHub Pull Request #1477
  

Backported to: 4.0.0-beta-3, 3.9.7

[jira-importer]

Matthew Jason Benson commented

Maven 4.x impl @ #1446

[jira-importer]

Matthew Jason Benson commented

#1447 is a 3.9.x specific implementation of this request. It differs greatly from the 4.x implementation due to the latter utilizing v4-specific APIs. I would love some guidance as to what modifications I can make to reach a state of acceptability for inclusion in any future 3.9.x release.

[jira-importer]

Matthew Jason Benson commented

Should we also update https://github.com/apache/maven-site/blob/master/content/apt/guides/introduction/introduction-to-profiles.apt (both streams)?