[6262] Switch to Spring Boot 4

[mcharfadi]

Pull request template

General purpose

What is the main goal of this pull request?

• Bug fixes
• New features
• Documentation
• Cleanup
• Tests
• Build / releng

Project management

• Has the pull request been added to the relevant project and milestone? (Only if you know that your work is part of a specific iteration such as the current one)
• Have the priority: and pr: labels been added to the pull request? (In case of doubt, start with the labels priority: low and pr: to review later)
• Have the relevant issues been added to the pull request?
• Have the relevant labels been added to the issues? (area:, difficulty:, type:)
• Have the relevant issues been added to the same project and milestone as the pull request?
• Has the CHANGELOG.adoc been updated to reference the relevant issues?
• Have the relevant API breaks been described in the CHANGELOG.adoc? (Including changes in the GraphQL API)
• In case of a change with a visual impact, are there any screenshots in the CHANGELOG.adoc? For example in doc/screenshots/2022.5.0-my-new-feature.png

Architectural decision records (ADR)

• Does the title of the commit contributing the ADR start with [doc]?
• Are the ADRs mentioned in the relevant section of the CHANGELOG.adoc?

Dependencies

• Are the new / upgraded dependencies mentioned in the relevant section of the CHANGELOG.adoc?
• Are the new dependencies justified in the CHANGELOG.adoc?

Frontend

This section is not relevant if your contribution does not come with changes to the frontend.

General purpose

• Is the code properly tested? (Plain old JavaScript tests for business code and tests based on React Testing Library for the components)

Typing

We need to improve the typing of our code, as such, we require every contribution to come with proper TypeScript typing for both changes contributing new files and those modifying existing files.
Please ensure that the following statements are true for each file created or modified (this may require you to improve code outside of your contribution).

• Variables have a proper type
• Functions’ arguments have a proper type
• Functions’ return type are specified
• Hooks are properly typed:
  • useMutation<DATA_TYPE, VARIABLE_TYPE>(…)
  • useQuery<DATA_TYPE, VARIABLE_TYPE>(…)
  • useSubscription<DATA_TYPE, VARIABLE_TYPE>(…)
  • useMachine<CONTEXT_TYPE, EVENTS_TYPE>(…)
  • useState<STATE_TYPE>(…)
• All components have a proper typing for their props
• No useless optional chaining with ?. (if the GraphQL API specifies that a field cannot be null, do not treat it has potentially null for example)
• Nullable values have a proper type (for example let diagram: Diagram | null = null;)

Backend

This section is not relevant if your contribution does not come with changes to the backend.

General purpose

• Are all the event handlers tested?
• Are the event processor tested?
• Is the business code (services) tested?
• Are diagram layout changes tested?

Architecture

• Are data structure classes properly separated from behavioral classes?
• Are all the relevant fields final?
• Is any data structure mutable? If so, please write a comment indicating why
• Are behavioral classes either stateless or side effect free?

Review

How to test this PR?

Please describe here the various use cases to test this pull request

• Has the Kiwi TCMS test suite been updated with tests for this contribution?

[mcharfadi]

I'll organize the PR in several commits when it's building.

[mcharfadi]

Here the most impacting changes :

• Replace com.fasterxml import package to tools.jackson

• Change the parameter of ICustomNodeStyleDeserializer and IRepresentationDeserializer handle method from
  INodeStyle handle(ObjectMapper mapper, String root) throws JsonProcessingException; to
  INodeStyle handle(ObjectNode root, JsonParser jsonParser, DeserializationContext context) throws JacksonException;
Optional<IRepresentation> handle(JsonParser jsonParser, DeserializationContext context, ObjectNode root);

• JsonProcessingException is replaced by JacksonException

• The method used to parse JSON have been updated accordingly to the Jackson migration guide.

• MapperFeature.SORT_PROPERTIES_ALPHABETICALLY & DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES have been disabled (as it were in Jackson 2) see ObjectMapperConfiguration

• jackson-datatype-jsr310 has been remove since it's included with Jackson3

• JacksonMappingProvider in tests has been removed since it's not compatible with Jackson 3

• Rest Controllers have been updated to not pass explicitly null to the body of the ResponseEntity.

• EObjectJsonSerializer has been updated and is now configured thanks to TestsConfigMapper instead of RestResponseSerializationCustomizer

• org.springframework.boot.test.web.client.TestRestTemplate has been replaced by org.springframework.web.client.RestTemplate

• StartMessage is now a record, as this class was not serializing correctly with Jackson3

• "sirius-components-charts", code coverage was set to 84.0 because the constructor of Hierarchy was not called by Jackson during the tests.

Feel free to squash the commits into one

[pcdavid]

Note that 4.0.5 has just been released: https://spring.io/blog/2026/03/26/spring-boot-4-0-5-available-now

[pcdavid]

Mention the exact version number.

[mcharfadi]

I'm now using 4.0.0 in the pom.xml

[pcdavid]

Any reason not to switch directly to 4.0.5?

[sbegaudeau]

I'll add a commit to switch to 4.0.5 since it should be just a single line to change.

[sbegaudeau]

We can't upgrade to liquibase 5.x

[mcharfadi]

I forced the use of liquibase 4 in dependency management

[sbegaudeau]

Imports need to be re-ordered

[mcharfadi]

done

[sbegaudeau]

This seems good, I've rebased it and handled the conflicts. I'll wait for the build to see the result and merge it if I don't encounter any issue. I'll try to add a couple of minor PRs too and perform a new release soon to open the possibility for downstream projects to switch to Spring Boot 4 too.