Page History

The developer is based on Eclipse 4.17 (2020.09) which now requires Java 11.
This is not a problem with our default installation because we ship and run the developer with Java 15.0.1
But developer using there own java, can't use Java 8 anymore to run Servoy 2020.12
Also upgraded a lot of other developer plugins libraries to be up to date to move our self to Java 11 later on.
Currently the runtime still supports Java 8 (so the WAR that you generate and deploy)
This will change in 2021 very likely the 20202021.03 (LTS) will be the last that supports Java 8, so maybe 2021.06 or 2021.09 and later will fully require java 11

...

If you implement your own (custom) components and you want to support such directive like keylistener you have to use the svy-attributes directive on components html: SvyAttributes directive

> By default Servoy will not query anymore for related data if the relation is a pk→fk relation and the parent record is not yet stored in the database. This can be controlled by a property see: Tuning the Server#Foundsetloadingandsavingtuning

know issue

>  f you use a repository_server thats not done in an inmemory table and you created that repository_server with a 2020.09 release then it could be that when upgrading to 2020.12 you will get a "upgrade repository" button on the admin page.
But that then bombs out with a primary key violation if that is the case you can fix that by running this statement on your database "repository_server" first:

...

because you are already on a repo version 53 but the the whole system doesn't know that yet.

> solution uploads (.servoy file) to the admin page could result in a file already exist() error, quick fix for this is to use the file-upload.jar of an older (2020.09) version of servoy