(Created page with "This page lists optional manual migration steps what you should do when going to upgrade J2Chrono or ChronoFly version 1.2.x to 1.3.x. All steps can be performed before of af...") |
|||
Line 1: | Line 1: | ||
− | This page lists optional manual migration steps what you | + | This page lists optional manual migration steps what you can do when going to upgrade J2Chrono or ChronoFly version 1.2.x to 1.3.x. |
− | All steps can be performed before | + | All steps can be performed before or after running the installation. |
==Remove old Java 7 runtime== | ==Remove old Java 7 runtime== |
Revision as of 00:01, 2 May 2020
This page lists optional manual migration steps what you can do when going to upgrade J2Chrono or ChronoFly version 1.2.x to 1.3.x.
All steps can be performed before or after running the installation.
Remove old Java 7 runtime
Proceed with this step only if you are sure you don't have any application (except J2Chrono or ChronoFly) installed to your operating system that requires this Java 7 runtime installation to be present.
Windows
- Remove directory
C:\Program Files (x86)\J2Chrono\jre
Linux
- Remove directory
/usr/lib/jvm/jre1.7.0_80
Upgrade plugins
Since JavaScript plugin engine has been upgraded from Rhino to Nashorn, following change is proposed to be done in every plugin .js file.
- Add following line to the beginning of plugin .js file
load("nashorn:mozilla_compat.js");
Plugin .js files can be found from following directories.
Windows
- Plugins directory
C:\Program Files (x86)\J2Chrono\chromo\plugins
Linux
- Plugins directory
/usr/lib/chromo/plugins