Kai Burjack created MNG-6297:
--------------------------------
Summary: Active-by-default profiles do not get activated when
JDK-activated profile matches
Key: MNG-6297
URL: https://issues.apache.org/jira/browse/MNG-6297
Project: Maven
Issue Type: Bug
Components: core
Affects Versions: 3.5.2, 3.5.0
Environment: Windows 7 x64, Windows 10 x64, jdk 1.8.0, jdk 9.0.1
Reporter: Kai Burjack
Priority: Major
When having a profile which whose activation condition is a jdk version, such
as 1.8, and below that another profile whose activation condition is
"by-default" then only the first profile (the one with the JDK version
condition) is active when building without explicitly defining any profile via
`-P`, such as when using `mvn clean package`.
This appeared for me the first time when actually using an jdk-activated
profile and an active-by-default profile for the first time in Maven 3.5.0.
After updating to 3.5.2 (current as of now) the problem still remains. It is
unclear whether any older Maven versions are affected by this behaviour.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
