User Tools

Site Tools


user-guide:common-changes-when-updating-groimp-1.5-to-2.0

The release of GroIMP 2.0 is based on java 11 (compared with java 1.7 before) and many dependencies have been updated. Thus, there might be some changes required when running previous models.

A non exhaustive list:

  1. Use –Xverify:none (= to -noverify) when starting GroIMP as a java command (e.g. `java -Xverify:none -jar core.jar`). There are some “differences” between the bytecode references used by Groimp compilation units, and the one used by the jvm. Java 1.7 didn't paid it attention, java 1.8 was more permissive, but now java 11 want to prevent it.
  2. Package org.apache.commons.math3, previously commons-math package was called org.apache.commons.math, the new version added a 3 in the name.
  3. Package de.grogra.gpuflux. Some functions from de.grogra.imp3d have been moved to de.grogra.gpuflux.imp3d to match the package name (Java 11 forbid package name split). So if you are using objects, lights or shaders from gpuflux, they should be imported as de.grogra.gpuflux.imp3d.xxx.
  4. Package org.apache.poi.ss to work with Microsoft documents (excel). The package have been updated and some of the cell access have changed (e.g. Cell.CELL_TYPE_STRING is now CellType.STRING). Please refer to the official documentation.
  5. const, the const key word was used to define variable as static final. However, to access modify the variable, they should not be final (except if they represent a reference). You can simply change all const to static
user-guide/common-changes-when-updating-groimp-1.5-to-2.0.txt · Last modified: 2024/04/12 12:19 by gaetan