A issue has been raised and fixed in apache/logging-log4j2: https://github.com/apache/logging-log4j2/issues/1783
A detailed explanation of the proposed change may be found in this issue.
Basically, the null check for the environment is not necessary in the builder as the isCondition() method already correctly checks for a null environment.
Comment From: pivotal-cla
@timgrohmann Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@timgrohmann Thank you for signing the Contributor License Agreement!
Comment From: mhalbritter
@philwebb As Log4j seems to have it's own SpringProfileArbiter which looks like ours, could we use that?
Comment From: wilkinsona
I don't think we can do that as it would introduce an (even stronger) cyclic dependency between the two projects.
Comment From: timgrohmann
Can we still integrate the upstream change into this project to fix the problem for Spring Boot users?
Comment From: mhalbritter
Yeah, I'll flag it to talk about it in our team meeting.
Comment From: mhalbritter
Thank you very much and congratulations on your first contribution :tada:!