We are pleased to announce the availability of Servoy 2019.06.1 (release number 3503)
This version is available through the the download site
We ship from now on by default only archive installers, so for windows a zip file and for osx/linux tar files.
That people can just extract and run. For OSX you need to make sure you follow a few steps (run firstuse.command first and then allow the app to run)
The full installers/archives are only for new installs, never use that to update/overwrite an existing install, existing installations should always be updated through the "check for updates".
This release can be updated by using the "latest" url: http://download.servoy.com/developer/latest/ (when you come from 2019.03 or higher)
If you install a clean install besides the current one which is 2019.03 or lower, be aware that the workspace will be upgraded and it is not recommended to use an upgraded workspace with an older release again.
If check for updates says there are no updates, then it could be a caching problem of eclipse, please restart the developer once and try again.
We now ship a java with our installation (Java 12). So there doesn't need to be a java installed on the system anymore.
Also with a next update, we can update the java version with it so no need to keep it up to date yourself anymore.
The update site can't be used to upgrade from 84 to this release, a bug in the eclipse update mechanisme will result in a broken installation.
So a clean install needs to be done if you come from 84 (but you can reuse the existing workspace just fine)
This is a release in our quarterly release cycle, if you want to stay on the LTS path you need to stick to 2019.03.1 and enabled only the lts update site.
For more information for the 2019.06 release check: 2019.06
This is a minor release only fixing 2 regressions found in the 06 final release and some small checks.
* Export of .servoy solution files could result in a wrong export where a specific set of properties (like tabSeq) where not correctly exported.
* Parsing of dates when assigning a date as a string to a date field (record.mydate = "2019-07-16") was to strict now because of the update of the time library
* Null check in the form editor
* Fixed accidental http session invalidation (after 1 minute) in very specific scenario.