We have migrated some non-a12 applications to Java 25.
For testing I also did the same migration with an A12 application and it seems to work fine.
Anything in particular I should consider? Is there a really strong general recommendation?
(This a12 application itself is neither production-relevant and nor busines-critical, so maybe a good candidate for an early migration.)
Please see the Java Version Policy on GetA12 .
Official support for Java 25 is planned for the A12 release line 2026.06.
In 2025.06 we do not and will not test with Java 25, i.e. it is kind of at your own risk.
Thanks a lot Ansgar!!
A big problem with the current documentation is that the search is so bad.
The page you linked isn’t even anywhere in the search results when I search for “Java Version” even though that exact term occurs in the heading.
Instead the top results are something about the definition of a version in the notification center, same for uaa, same for print engine, something about Java artifacts in the kernel, …
It’s a pity because the documentation is really extensive nowadays and there clearly has been much work spent on it.
Hi Stephen - agreed, search in GetA12 should be improved.
So far, search is limited to documentation and does not include content from pages nor from blog posts. We have A12DOC-688 to extend the index and include this. I assume that this will allow us to improve the overall search experience.
A matter of priority now…