Servoy 2019.09

Classic Servoy
1

We are pleased to announce the availability of Servoy 2019.09 (release number 3522)

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.09 release check: Whats new

2

Hi

We have a third party component that is not yet supported by Java 12 so is it possible to override the supplied Java version?

Thanks

3

yes just change the servoy.ini file

But i wonder more how it is not supported. The lib uses internal api that is removed? (like com.sun.xxx stuff)

4

It is something to do with the signing of the Jar files. We get an error that says:

SecurityException: Signers of 'com.aspose.pdf.internal.l72v.$Proxy191' do not match signers of other classes in package

And their support have come back and said it is because they don’t support Java 12 yet and we should revert to Java 8

That’s easy to do on the server but I didn’t know how to do it in developer

Thanks

5

Reverting to Java 8 has cleared the problem

Thanks

6

but that error is really weird, that you get a signing error like that
that shouldn’t have anything todo with java 8 or java 12… That is just not allowed or the signing stuff is somehow old/wrong and java 12 doesn’t accept that anymore (you can always remove the singing stuff if you don’t use smart client )

7

NG only :D

Will try removing the signing now and see what happens.

Thanks for that suggestion as I would much rather stick with a standard developer install.

8

Love it! :D

9

Can’t download the installer. There’s an error NET::ERR_CERT_COMMON_NAME_INVALID

10

Firefox reports this:

https://download.servoy.com/downloads/lts/servoy_installer.jar

Unable to communicate securely with peer: requested domain name does not match the server’s certificate.

HTTP Strict Transport Security: true
HTTP Public Key Pinning: false

Looks like the download.servoy.com URL uses a Amazon S3 certificate.

Common Name: *.s3.amazonaws.com

11

dont use https for that this should work fine: http://download.servoy.com/downloads/lt … taller.jar

12

Thank you for bringing this up; it is fixed now.

13

Thanks you!

14

I have noticed that there are no issues reported for Servoy 2019.09 that will be backported to a 2019.09.02 release.
No release 2019.09.02 is planned.

I thought every quarterly Servoy release has it’s LTS path right?

Regards,

15

no
only the YEAR.03 is promoted as a LTS (we will release a 2019.03.x in the coming month)

all others so YEAR.06,09,12 are following each other directly.
so 2019.09 is already replaced now with 2019.12 there wont be another release of 2019.9.x
if we find a serious issue in 2019.12.0 that is just released we will do a release 2019.12.1 for that, if not then 2020.03 will replace 2019.12 at the end or March, beginning of April

Then 2020.03 will be promoted later that year as a LTS release so it could be that we release 2020.06 (that replaces the latest stream of 2020.03) at the same time with 2020.03.1_LTS (that kind of replaces the 2019.03.x_lts release)

So we will have quarterly “latest” releases
and yearly LTS releases based on the YEAR.03 latest release.

16

Thanks for clarifying Johan!

Regards,