We are pleased to announce the availability of Servoy 2023.12.2 (release number 3924)
This is a security release, please upgrade to this release if you are on a 2023.06 or higher release.
If you are on LTS release or any older version please upgrade to 2022.3.7 LTS or 2023.3.5 LTS
This version is available through the download site
An installation (coming from the normal installer or from a platform specific archive) is shipping with a Java VM (Java 21.0.1)
So for the platform specific archives you don’t need to install or have java on your system.
This release can be updated by using the “latest” url: http://download.servoy.com/developer/latest/ (when you come from 2019.03 or higher)
This release is build on Eclipse 2023.09 (4.29)
This is a release in our quarterly release cycle
if you want to stay on the LTS path you need to stick to 2023.03.5 LTS and enabled only the lts update site.
please also update the webpackages that also have releases for 2023.12
If coming from a much older release like 2022.03 then you first have to updated to 2023.03 and then go to 2023.12
This is because of an Eclipse update bug that prevents these updates.
I just upgraded a copy of Servoy that I had installed from build 3922 to 3924, but I am unable to ‘upgrade the repository’
When I launch Developer shows the normal message about the workspace being on 3922 & needing to upgrade to 3924, but then it fails instantly and suggests doing it from the command line.
I then tried in Terminal to go to the application_server directory & then run
./servoy_server.sh -upgradeRepository
which returns the prompt very quickly, but no other messages/errors/output
When I re-open Developer, it still needs the repo upgrading!
Developer has a working connection to the repository_server database.
I also tried
java -jar servoy_updater.jar
and
java -jar servoy_updater.jar -releaseNumber 3924
, which both display
Current Servoy version 2023.12.0.3922
Checking for new Servoy version
Working in directory: /Applications/Servoy ProConf NG.app/Contents
Loading version info...
No update found, if you want beta versions start with option: -beta or use -lts to force to go to a LTS stream
Done, Servoy can be started
HELP!???
(I am using an M2 MacBook Pro and have updated other copies of Servoy to latest version without having this issue , so am at a loss as to what is wrong & what to do now…
patrick:
Hi Rafi,
I don’t really follow. Developer does not use the repository at all. When you say
but then it fails instantly and suggests doing it from the command line
what exactly is suggested?
These are the dialogs I get…
[attachment=1]Screenshot of Servoy Developer at 21 Feb 2024 at 14_21_46.png[/attachment]
[attachment=0]Screenshot of Servoy Developer at 21 Feb 2024 at 14_21_59.png[/attachment]
Hope that clarifies…
I had the same issue when updating.
When I installed a fresh version it worked, the repository could not be updated when I did a normal update.
I know it’s all ok with fresh install, but I have managed to upgrade other older version & the repo did get upgraded in normal way, just this one is having an issue…
I guess I might just have to install a fresh newest version & connect to my workspace…
Problem is that the updater tries to get a file from a http site instead of https and we enforced it at this moment to be https (http gets a redirect)
but the code is a simple url get (not a full blown http client that follows redirects) so it doesn’t download the install file correctly and can’t upgrade because of that
I already fixed this for the next release of the various branches to use the https site not http. But there is currently not an easy fix for you guys to do (like overwrite the servoy_update.jar, that will not work)
the application server is for the shouldn’t be used anymore please make sure you move away from that (and use a real install of tomcat with a WAR)
But a developer is just updated through update site url so if you really want to go to this version: https://download.servoy.com/developer/latest/3924
but do remember this is not a supported version and more, please move to an LTS version (or a current one so 24.12)
