You only need to transform the javax.* packages that are part of the EE8 specification. There are other JDK classes that need to remain in their original javax.* packages. The javax.rmi.* packages can be ignored for transformation.


On Wed, Nov 17, 2021 at 3:41 PM Tomasz Adamski <tadamski@redhat.com> wrote:
When I was trying to establish the steps needed to transform OpenJDK project to Jakarta namespace I noticed that a substantial part of the codebase implements RMI-IIOP protocol (which relies on javax.rmi.* packages). This seems tricky to
transform IMO. Although all those classes are included into the project and technically I could just rename the package, logically it doesn't make much sense to me because there is no such thing as jakarta.rmi and this makes even less sense in a project whose goal is to provide interoperability.

I'm also not sure how this is supposed two work from a legal point of view: if Jakarta allows for optional implementation of RMI-IIOP maybe I could just leave it this way or are we legally required to get rid of all javax.* naming from the codebase?

Regards,
Tomek
_______________________________________________
wildfly-dev mailing list -- wildfly-dev@lists.jboss.org
To unsubscribe send an email to wildfly-dev-leave@lists.jboss.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s