I could package Freeplane for Windows with Java 11 or Java 15, it would help to avoid this problem, but if someone would run Freeplane under Java 17 it would appear for this user again. There is nothing I could do if we want to allow running Freeplane under Java 17. Particularly, I think that in the case shared by use of the field children instead of the method children() is less safe because the field value might be null. You can get some background information from Therefore you can not access such protected fields from groovy scripts and formulas any longer. In Java 17 access to protected fields of internal java modules by reflection has been restricted.
FREEPLANE FIND AND REPLACE HOW TO
So let us discuss how to handle this problem.īeta Was this translation helpful? Give feedback.
If the called private methods were annotated with or their visibility could be changed to package private it would fix the issue, but I am not sure if and how fast we could get Groovy devs to accept this change. I do not have any ideas how to work around it on our side. The bug was reported in 2007 and it does not look like they are going to fix it. Therefore the new Console class can not be used as a base class for any other classes. Unfortunately, I have seen that popular add-on WikdShell and related add-on Freeplane_WikdShell_Extension by are heavily incompatible with Groovy 4.0.1 because package groovy.ui and class groovy.ui.Console has been removed and the Console contained in replacement package can not be used as a base class for WikdShell and WikdExtension because of Groovy bug entitled "Closure in base class unable to call private methods when invoked from derived class". It contains the latest versions of all used libraries including the latest Groovy 4.0.1. I have released the first preview version of Freeplane 1.10.x which has the same functionality as Freeplane 1.9.14 but works with Java 15, 16, and 17.
0 kommentar(er)
