Dear Java developers, nerds and geeks,
We’re thrilled to break some exciting news. The much-anticipated TomEE 10 (Plume distribution) has finally arrived in SAP Java Buildpack 2! Buckle up as we dive into what this means for you and your applications.
Why Migrate from TomEE 7 to TomEE 10?
End of Life for SAP Java Buildpack 1
As you know from our previous blog post and release notes, SAP Java Buildpack 1 has been deprecated and will be removed from the SAP BTP, Cloud Foundry landscapes on June 30, 2025. TomEE 7 will be removed as well. Which means that, effective July 1, applications that still run on the old buildpack (and use TomEE 7) will fail during restage or redeploy.
Jakarta EE 10 Support
TomEE 10 is fully aligned with Jakarta EE 10, providing you with the latest EE specifications and tools for building modern enterprise applications.
Security Reinforcements:
TomEE 10 comes with the latest security patches and improvements, safeguarding your applications from potential threats.
How to Migrate?
Update your manifest.yml file. Replace tomee7 with just tomee. Replace sap_java_buildpack with sap_java_buildpack_jakarta.
For example:
—
applications:
– name: myapp
buildpack: sap_java_buildpack_jakarta
…
env:
TARGET_RUNTIME: tomee
JBP_CONFIG_OPEN_JDK_JRE: ‘{ jre: { version: 17.+ } }’
JBP_CONFIG_TOMEE: ‘{ tomee: { version: 17.+ } }’
2. Update Your Dependencies
Ensure that your application’s dependencies (see your pom.xml file) are compatible with Jakarta EE 10. If they’re using former Java EE javax.* packages, you need to migrate them to Jakarta EE jakarta.* ones. You can run the migration by using any of the available community tools.
For example: https://tomee.apache.org/javax-to-jakarta.html
See also: Migrate your Applications to SAP Java Buildpack 2
3. Test, Test, Test!
Before you deploy to production, make sure to thoroughly test your application in a staging environment.
Don’t Wait, Migrate!
The clock is ticking, and June 30 will be here before you know it. But no worries, you can do it! 
Happy migrating and coding with TomEE 10 and SAP Java Buildpack 2! 
Dear Java developers, nerds and geeks,We’re thrilled to break some exciting news. The much-anticipated TomEE 10 (Plume distribution) has finally arrived in SAP Java Buildpack 2! Buckle up as we dive into what this means for you and your applications. Why Migrate from TomEE 7 to TomEE 10? End of Life for SAP Java Buildpack 1 As you know from our previous blog post and release notes, SAP Java Buildpack 1 has been deprecated and will be removed from the SAP BTP, Cloud Foundry landscapes on June 30, 2025. TomEE 7 will be removed as well. Which means that, effective July 1, applications that still run on the old buildpack (and use TomEE 7) will fail during restage or redeploy. Jakarta EE 10 Support TomEE 10 is fully aligned with Jakarta EE 10, providing you with the latest EE specifications and tools for building modern enterprise applications. Security Reinforcements: TomEE 10 comes with the latest security patches and improvements, safeguarding your applications from potential threats. How to Migrate? Update your manifest.yml file. Replace tomee7 with just tomee. Replace sap_java_buildpack with sap_java_buildpack_jakarta. For example: —
applications:
– name: myapp
buildpack: sap_java_buildpack_jakarta
…
env:
TARGET_RUNTIME: tomee
JBP_CONFIG_OPEN_JDK_JRE: ‘{ jre: { version: 17.+ } }’
JBP_CONFIG_TOMEE: ‘{ tomee: { version: 17.+ } }’ 2. Update Your Dependencies Ensure that your application’s dependencies (see your pom.xml file) are compatible with Jakarta EE 10. If they’re using former Java EE javax.* packages, you need to migrate them to Jakarta EE jakarta.* ones. You can run the migration by using any of the available community tools. For example: https://tomee.apache.org/javax-to-jakarta.html See also: Migrate your Applications to SAP Java Buildpack 2 3. Test, Test, Test! Before you deploy to production, make sure to thoroughly test your application in a staging environment. Don’t Wait, Migrate! The clock is ticking, and June 30 will be here before you know it. But no worries, you can do it! Happy migrating and coding with TomEE 10 and SAP Java Buildpack 2! Read More Technology Blogs by SAP articles
#SAP
#SAPTechnologyblog
