Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

timgrohmann
Copy link
Contributor

A issue has been raised and fixed in apache/logging-log4j2: apache/logging-log4j2#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.

@pivotal-cla
Copy link

@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.

@pivotal-cla
Copy link

@timgrohmann Thank you for signing the Contributor License Agreement!

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Feb 5, 2024
@mhalbritter
Copy link
Contributor

mhalbritter commented Feb 6, 2024

@philwebb As Log4j seems to have it's own SpringProfileArbiter which looks like ours, could we use that?

@wilkinsona
Copy link
Member

I don't think we can do that as it would introduce an (even stronger) cyclic dependency between the two projects.

@timgrohmann
Copy link
Contributor Author

Can we still integrate the upstream change into this project to fix the problem for Spring Boot users?

@mhalbritter
Copy link
Contributor

Yeah, I'll flag it to talk about it in our team meeting.

@mhalbritter mhalbritter added the for: team-meeting An issue we'd like to discuss as a team to make progress label Feb 19, 2024
@philwebb philwebb added type: bug A general bug and removed status: waiting-for-triage An issue we've not yet triaged for: team-meeting An issue we'd like to discuss as a team to make progress labels Feb 22, 2024
@philwebb philwebb added this to the 3.1.x milestone Feb 22, 2024
@mhalbritter mhalbritter self-assigned this Feb 28, 2024
@mhalbritter
Copy link
Contributor

Thank you very much and congratulations on your first contribution 🎉!

@mhalbritter mhalbritter modified the milestones: 3.1.x, 3.1.10 Feb 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug A general bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants