Ralf created MENFORCER-286:
------------------------------
Summary: requireProperty from active profiles are incorrectly mixed
Key: MENFORCER-286
URL: https://issues.apache.org/jira/browse/MENFORCER-286
Project: Maven Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Affects Versions: 3.0.0-M1
Environment: Apache Maven 3.3.9
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References
20170722_357405 (JIT enabled, AOT enabled)
Reporter: Ralf
Attachments: pom.xml
I have two profiles that both use the enforcer plugin to check some properties.
* profile1 checks the property "test.user" for the value "tester"
* profile2 checks that the property "inttest.user" is set.
If either profile is enabled everything works fine.
If both profiles are enabled the property "intest.user" is tested for the value
"tester". That fails.
The problem depends on the ordering of the profiles in the pom. If I move
profile2 above profile1 everything works fine. Unfortunately I can't use this
workaround in my real live project.
Take the attached pom and run the following:
{code}
mvn validate # OK
mvn validate -Pprofile1 # OK
mvn validate -Pprofile2 # OK
mvn validate -Pprofile1 -Pprofile2 # FAILS
{code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
