Spring Framework 5 now builds against it so we should too
Comment From: wilkinsona
I've hit a stumbling block while trying to move off deprecated API: https://github.com/FasterXML/jackson-modules-java8/issues/16
Comment From: wilkinsona
This has been reverted due to https://github.com/FasterXML/jackson-databind/issues/1559 (see gh-7695)
Comment From: cowtowncoder
I hope to look into 1559 on jackson-databind ASAP now. If there are any other observed breakages, please let me know -- while I am not releasing pr2 quite yet I hope to do that relatively soon, but ideally not if there are pending issues with Spring Boot.
Comment From: wilkinsona
Thanks, @cowtowncoder. Much appreciated.
but ideally not if there are pending issues with Spring Boot.
I have successfully built our master branch against 2.9.0.pr1 after removing final from Status:
diff --git a/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/health/Status.java b/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/health/Status.java
index c3a5d89b70..095a233ddf 100644
--- a/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/health/Status.java
+++ b/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/health/Status.java
@@ -35,7 +35,7 @@ import org.springframework.util.ObjectUtils;
* @since 1.1.0
*/
@JsonInclude(Include.NON_EMPTY)
-public final class Status {
+public class Status {
/**
* {@link Status} indicating that the component or subsystem is in an unknown state.
I haven't committed that change as we do not want people to be able to subclass Status.
Other than FasterXML/jackson-databind#1559, there are no known issues with Spring Boot.
Comment From: cowtowncoder
Ok, I also did fix the root cause I think -- final just happened to trigger it, but I think that is not the only way for it to occur. Use of static typing should have similar effects.
I hope to wrap up pr2 to be released soon now.