cloudevents-bom has cloudevents-parent as its parent, and the parent's dependencyManagement imports jakarta.platform:jakarta.jakartaee-bom. The BOM inherits that import, so every project that imports cloudevents-bom also gets the whole Jakarta EE BOM.
In a Spring Boot 4 build this overrides the Jakarta API versions Spring Boot manages with the ones from the CloudEvents release (5.0.0 brings Jakarta EE 10). We had to stop importing the BOM and pin the CloudEvents modules one by one.
Only the restful-ws-jakarta modules need the Jakarta EE BOM, so the import can live there. With that change ./mvnw verify passes and help:effective-pom -pl bom no longer manages Jakarta artifacts. I'll open a PR.
cloudevents-bomhascloudevents-parentas its parent, and the parent'sdependencyManagementimportsjakarta.platform:jakarta.jakartaee-bom. The BOM inherits that import, so every project that importscloudevents-bomalso gets the whole Jakarta EE BOM.In a Spring Boot 4 build this overrides the Jakarta API versions Spring Boot manages with the ones from the CloudEvents release (5.0.0 brings Jakarta EE 10). We had to stop importing the BOM and pin the CloudEvents modules one by one.
Only the restful-ws-jakarta modules need the Jakarta EE BOM, so the import can live there. With that change
./mvnw verifypasses andhelp:effective-pom -pl bomno longer manages Jakarta artifacts. I'll open a PR.