Skip to content

Allow Spring arbiter with no Spring environment present#1836

Merged
ppkarwasz merged 1 commit intoapache:2.xfrom
ppkarwasz:spring-profile
Oct 6, 2023
Merged

Allow Spring arbiter with no Spring environment present#1836
ppkarwasz merged 1 commit intoapache:2.xfrom
ppkarwasz:spring-profile

Conversation

@ppkarwasz
Copy link
Contributor

Most Log4j configurations in Spring Boot are used twice: with no environment and with an environment present. Therefore the Spring Boot arbiter should not fail with no environment.

After adding required additional assertions in SpringProfileTest, only SpringLookupTest uses JUnit 4, so we migrate it to JUnit 5.

Fixes #1783.

@ppkarwasz ppkarwasz added this to the 2.21.0 milestone Oct 6, 2023
Most Log4j configurations in Spring Boot are used twice: with no
environment and with an environment present. Therefore the Spring Boot
arbiter should not fail with no environment.

Fixes apache#1783.
@ppkarwasz ppkarwasz merged commit 1187b78 into apache:2.x Oct 6, 2023
@ppkarwasz ppkarwasz deleted the spring-profile branch October 6, 2023 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

SpringProfile arbiter fails without a Spring's environment

1 participant