You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are working on branch struts6-upg.
Until now, we have replaced the namespaces from javax to jakarta, removed the javax libraries, upgraded relevant dependencies to be compatible with Jakarta EE.
We are encountering over 100 errors now due to myoscar removal. Will pause here now and come back to these errors later. (Ticket #102)
= Update on Dec 3 =
We need to first upgrade the following platform / framework to be prepared to migrate to Jakarta EE:
After upgrading above things, we can start to do the migration. We can use IntelliJ's refactor tool to do the migration, or rely on the dependencies of Eclipse Transformer (TBD)
We paused on this task temporarily as we learned that there are a lot of things that have to be done first before being able to migrate to Jakarta EE such as upgrading frameworks, java environment, and tomcat.
= First Note =
Created a branch jakarta-upgrade based off java11-upg branch. Migrate javax libraries to jakarta libraries.
Benefits:
possibility of upgrade to Java 17
possibility of upgrade to Tomcat 10
We split up the work to try and implement the Eclipse Transformer tool to help us migrate the javax libraries to jakarta. We used two methods:
.jar file
dependency/plugin
We have some little progress with the dependency/plugin as we were able to run it. But no changes were made in the files to migrate the javax libraries to jakarta.
With .jar file, the VSCode terminal is not letting us the .jar file yet, giving us errors. We assume that it was because of the permissions/restrictions in the Docker containers.
The text was updated successfully, but these errors were encountered:
= Update on Feb 19 =
We are working on branch
struts6-upg
.Until now, we have replaced the namespaces from
javax
tojakarta
, removed thejavax
libraries, upgraded relevant dependencies to be compatible withJakarta EE
.We are encountering over 100 errors now due to
myoscar
removal. Will pause here now and come back to these errors later. (Ticket #102)= Update on Dec 3 =
We need to first upgrade the following platform / framework to be prepared to migrate to Jakarta EE:
After upgrading above things, we can start to do the migration. We can use IntelliJ's refactor tool to do the migration, or rely on the dependencies of Eclipse Transformer (TBD)
We paused on this task temporarily as we learned that there are a lot of things that have to be done first before being able to migrate to Jakarta EE such as upgrading frameworks, java environment, and tomcat.
= First Note =
Created a branch
jakarta-upgrade
based offjava11-upg
branch. Migrate javax libraries to jakarta libraries.Benefits:
We split up the work to try and implement the Eclipse Transformer tool to help us migrate the javax libraries to jakarta. We used two methods:
We have some little progress with the dependency/plugin as we were able to run it. But no changes were made in the files to migrate the javax libraries to jakarta.
With .jar file, the VSCode terminal is not letting us the .jar file yet, giving us errors. We assume that it was because of the permissions/restrictions in the Docker containers.
The text was updated successfully, but these errors were encountered: