-
Notifications
You must be signed in to change notification settings - Fork 40.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SpringProfile arbiter fails without a Spring's environment #39403
Conversation
@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. |
@timgrohmann Thank you for signing the Contributor License Agreement! |
@philwebb As Log4j seems to have it's own SpringProfileArbiter which looks like ours, could we use that? |
I don't think we can do that as it would introduce an (even stronger) cyclic dependency between the two projects. |
Can we still integrate the upstream change into this project to fix the problem for Spring Boot users? |
Yeah, I'll flag it to talk about it in our team meeting. |
Thank you very much and congratulations on your first contribution 🎉! |
A issue has been raised and fixed in
apache/logging-log4j2
: apache/logging-log4j2#1783A 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.