javaspring-cloud/spring-cloud-kubernetes #870Not a task: not reproduced

Application fails to start on update from 2.0.3 to 2.0.4 if using spring-boot-starter-log4j2

envgap__spring-cloud__spring-cloud-kubernetes-870

Original GitHub issue ↗Dated source checkout ↗Opened 2021-09-24

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit: 10fea0f642f9c5f563c30e29e3a7878b02e6ba3c
Manifest: spring-cloud-kubernetes-commons/pom.xml
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

spring-cloud/spring-cloud-kubernetes #870 · read the original issue

I have an application using Spring Cloud K8s with a parent pom that declares spring-boot-starter-log4j2 as the dependency for logging.



Updating to 2.0.4 broke the application startup since spring-boot-starter-logging was a new dependency for Spring Cloud K8s. Could that be made optional? Or at least document that it should be excluded if you are using log4j2 with Spring Cloud K8s.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]