Currently, the Java code generators produce artifacts, that reference the javax namespace, primarily for validation related code.
With the migration of the javax namespace to jakarta this introduces problems now that more and more of our projects are fully migrated to later versions of all dependencies.
In this context most prominent to mention is a migration to Spring Boot 3+, which introduces this change at full extend.
In order to be able to produce artifacts that still work in such an environment, it is necessary that also the ESMF SDK and its artifact generators are migrated to the new jakarta namespace.
Currently, the Java code generators produce artifacts, that reference the
javax
namespace, primarily for validation related code. With the migration of thejavax
namespace tojakarta
this introduces problems now that more and more of our projects are fully migrated to later versions of all dependencies. In this context most prominent to mention is a migration to Spring Boot 3+, which introduces this change at full extend.In order to be able to produce artifacts that still work in such an environment, it is necessary that also the ESMF SDK and its artifact generators are migrated to the new
jakarta
namespace.