Similarly, as part of Java SE 5 (2004), the number 2 was removed from J2SE, when Google was not listed.
Because javax namespaces are no longer available, Jakarta EE provides a very clear demarcation line.
Jakarta 9 (2019 and beyond) uses the Jakarta namespace.
Java EE 5 (2005) to Java EE 8 (2017) uses javax namespaces.
Java EE 4 uses javax namespaces.
Wayne Beaton, marketing manager of the Eclipse Foundation, introduced ways to rename the specification itself. In addition to replacing "Java" with "Jakarta", it also brings consistency and clarity to each specification name. For example, there is no need for redundant word "API" in the API specification name.
Normative renaming has not yet standardized the package names of dependencies. For example, a new renamed specificationJakarta MailGroupId (formerly Java Mail) is com. sun. mail, and artifactId is jakarta. mail. andJakarta RESTful WebServices (formerly JAX-RS)GroupId is jakarta. ws. rs.ArtifactId is jakarta. ws. RS - api.
Some frameworks, such as MicroProfile, are using other parts of Jakarta EE or are being used by other parts of Jakarta EE. John Clingan in a post（MicroProfile is not equivalent to Jakarta EE) The difference between the two is clarified. Other frameworks, such as Quarkus, are combined with Jakarta EE to create a hybrid approach through which developers can choose the most appropriate tools for the problems they are solving.
Developers may not notice the renaming of the project because they only call the application library at the code level. For porting old applications, developers want to use compatible Jakarta EE applicationsThe serverOr Servlet containers, and ensure that their dependencies are used using new groupId and artifactId.