![]() ![]() On a Twitter thread, Milinkovich points out that these negotiations were extremely complex, and also notes that Oracle has made many substantial donations: Mark Little, JBoss technical lead for Red Hat, provided a personal and technical analysis on the significant effort needed for this refactoring. The change will likely trickle down into many non-EE web applications, including Spring web applications, as EE hosts the Java Servlet API, Java Mail API, and other critical components. This change will impact every API in EE, as they all begin with javax. ![]() The change in package-name removes any ambiguity of ownership, that Java EE 8 and below were developed under the stewardship of Sun and Oracle, and Jakarta EE 8 and above are guided by the Eclipse Foundation. This includes acronyms such as EJB, JPA or JAX-RS. Specification names must be changed from a "Java EE" naming convention to a "Jakarta EE" naming convention. Jakarta EE component specifications using the javax package namespace may be omitted entirely from future Jakarta EE Platform specifications. Jakarta EE specifications that continue to use the javax package namespace must remain TCK compatible with the corresponding Java EE specifications. No modification to the javax package namespace is permitted within Jakarta EE component specifications. The javax package namespace may be used within Jakarta EE specifications but may be used "as is" only. ![]() "The implications of this are as follows", Milinkovich wrote: Mike Milinkovich, executive director of the Eclipse Foundation, explained the end of negotiations for use of the javax.* package in an Eclipse Foundation blog post, " Update on Jakarta EE Rights to Java Trademarks." The post indicates the agreed-upon licensing rights for the historical package and represents a clear line for future implementations of Jakarta EE as its specification and Test Compatibility Kit evolve. As a result, all future updates and improvements to the framework made under the auspices of Jakarta EE will go into a different package name and require a migration of application and library code. Following many months of negotiations, the Eclipse Foundation and Oracle have been unable to agree on the terms of an agreement for the Eclipse Foundation community to modify the javax package namespace or to use the Java trademarks currently used in Java EE specifications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |