Replies: 3 comments 4 replies
-
After announcing the migration plans via mailing to a broad list of users we started to get some feedback. Several users have constraints for the migration. We know already some of them cannot do it until the end of 2024. Others do not have complaints about Jakarta but will need Java 8 compatible version for a longer time. So the idea is to continue with the release, but we should keep the migration to the minimal. In this sense, I think Jakarta could be migrated to EE 9 (XML bindings 3.0) instead of Jakarta EE 10. Spring Boot 3 is based on Jakarta EE 9. Regarding a possible split of the migration between Java 11 and Jakarta that does not seem to be necessary. Anyway we will need to maintain the Java 8 Jaxb version for at least a couple of years. |
Beta Was this translation helpful? Give feedback.
-
Are you sure that Spring Boot 3 is based on Jakarta EE 9? I agree that it is not clear, If we read this very old blog post , we can assume so, but if we read the release note and check the code, it seems that thery have migrated to XML binding 4.0 which is part of Jakarta EE 10, don't you agree? |
Beta Was this translation helpful? Give feedback.
-
RC1 has been released https://central.sonatype.com/artifact/com.prowidesoftware/pw-iso20022/SRU2022-10.0.0-RC1 Including:
The corresponding Prowide Core dependency has also been release as RC1 with analogous changes: https://central.sonatype.com/artifact/com.prowidesoftware/pw-swift-core/SRU2022-10.0.0-RC1 |
Beta Was this translation helpful? Give feedback.
-
I start this topic to talk about the migration that we are carrying out, to get some community users feedback as well on this regard.
From @essobedo PR initiative:
Motivation
Many frameworks like Spring Boot, Quarkus, Camel... have made the Jakarta EE 10 migration which makes the lib incompatible with them. The goal of these changes is to migrate the lib to make it compatible again with the frameworks.
Beta Was this translation helpful? Give feedback.
All reactions