Skip to content
Merged
Changes from 6 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions java/migration.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,16 +53,18 @@ Here, the *migration* `com.sap.cds.services.migrations.MigrateStatements` from C

### Spring Boot 4

CAP Java 5 uses Spring Boot 4 as underlying framework. Consult the [Spring Boot 4.0 Migration Guide](https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide) for changes between Spring Boot 3.5 and Spring Boot 4.0.
CAP Java 5 uses Spring Boot 4 and Spring Security 7 as underlying framework. Unless a CAP Java application is not using native Spring APIs, Spring Boot 4 incompatibilities should only affect renaming of maven dependencies and smaller changes in test classes (e.g. changed package name of `AutoConfigureMockMvc`). Consult the [Spring Boot 4.0 Migration Guide](https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.0-Migration-Guide) for changes between Spring Boot 3.5 and Spring Boot 4.0. For changes between Spring Security 6.5 and 7 refer to the [Spring Security 7 Migration Guide](https://docs.spring.io/spring-security/reference/migration/).

In any case, it is required to upgrade the [BTP Security Library](https://github.com/SAP/cloud-security-services-integration-library) to version > 4.0.0.

### Minimum Versions

CAP Java 4.0 increased some minimum required versions:
CAP Java 5.0 increased some minimum required versions:

| Dependency | Minimum Version |
| --- | --- |
| Spring Boot | 4.0 |
| XSUAA | TBD |
| XSUAA (BTP Security Library) | 4.0.0 |

## CAP Java 3.10 to CAP Java 4.0 { #three-to-four }

Expand Down
Loading