Skip to content

Conversation

@DavidIAm
Copy link

https://github.com/spring-projects/spring-boot/commits/decc32dde3c04c980466f6f5bc7b25f17ca99c69/spring-boot-project/spring-boot-servlet/src/main/java/org/springframework/boot/servlet/autoconfigure/MultipartProperties.java?browsing_rename_history=true&new_path=module/spring-boot-servlet/src/main/java/org/springframework/boot/servlet/autoconfigure/MultipartProperties.java&original_branch=0b601118bdc3c35d161c9ae58e25d9b104609a65

They moved this around per the spring framework commit linked. I'm not sure this is the right answer in totality, but... its a start. For instance, its unclear to me how this can exist in BOTH situations of 3.5 compatibility and 4.0 compatibility - maybe some of the conditional-on-class type annotations could alternate between two different possible beans or something?

@davsclaus
Copy link
Contributor

Camel is not spring boot v4 compatible. We only support 3.5.x.

@DavidIAm
Copy link
Author

Camel is not spring boot v4 compatible. We only support 3.5.x.

Oh. I see. And here I wanted versions of transitive dependencies spring 4 utilizes in my camel-spring-boot application. I'm sure this particular categorical statement is not going to last forever; is there any expression of dependency that will indicate when such a compatibility shift/attempt will likely be started?

@davsclaus
Copy link
Contributor

later this year towards the next LTS in Q1 2026

@davsclaus
Copy link
Contributor

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.

2 participants