Servoy 2023.09 release candidate 1

[jcompagner]

We are pleased to announce the availability of Servoy 2023.9 release candidate 1 (release number 3900)

See whats new for the global changes and the case list

For Windows the installer: exe
and for the MacOSX_86_64 we have an native dmg
and for the MacOSX_Aarch64 (M1) we have an native m1 dmg
for linux it is tar.gz

For windows we also still have just the zip

An installation (coming from the normal installer or from a platform specific archive) is shipping with with a Java VM (Java 17.0.
So for the platform specific archives you don't need to install or have java on your system.

This release is build on Eclipse 2023.06 (4.28)


The developer can be updated by the https://download.servoy.com/developer/l ... ecandidate update site url.
This is in our "latest" release stream (03,06,09,12) if you want to stick the LTS release then disable that releasecandidate url and stick to the urls with "lts" in the name
If you update to this release you have to do a new install of 2023.03.4_LTS to go back to an the LTS release branch

it could be that the update fails if you come from a much older release (like 2021.06 -> 2022.12) that you can get errors like:

Code: Select all

An error occurred while collecting items to be installed
session context was:(profile=DefaultProfile, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
Problems downloading artifact: osgi.bundle,com.servoy.eclipse.core,2022.12.0.3840_rc.
Error reading signed content:C:\Users\jcomp\AppData\Local\Temp\signatureFile11879913363204093521.jar


Or that you can't install it completely (you can't pass the update dialog, because it says incompatibilities found)
This is because from 2022.12 on we depend on java 17. (so the developer that you run should already be on java 17)

You can fix both issues to first jump to an older version like a 2022.03.x release, you can do this by making this url:

https://download.servoy.com/developer/latest/3743/

first the only update site in the preferences -> install/update -> sites, so add that url and make sure that is the only one.

Then it updates to that release first, then you can enable the release_candidate url again.

[rienk]

Within my solution I use the block ui package. I have an empty form editor when the package has a higher version than 1.0. When I then start the solution I get an empty page!

[emera]

What error do you get in the Titanium NG build console?
I just installed the latest svyBlockUI (v2023.6.0) and it works for me.

[rienk]

When i start the solution, i get the following error in de browser console:

core.mjs:5205 JIT compilation failed for NgModule class BlockUIModule {
static forRoot(settings = {}) {
return {
ngModule: BlockUIModule_1,
providers: [{
provide: BlockUIModuleSettings,
useValue: settings
}, {
…
getCompilerFacade @ core.mjs:5205
Show 1 more frame
Show less
core.mjs:10920 ERROR Error: Uncaught (in promise): Error: The NgModule 'BlockUIModule' needs to be compiled using the JIT compiler, but '@angular/compiler' is not available.

JIT compilation is discouraged for production use-cases! Consider using AOT mode instead.
Alternatively, the JIT compiler should be loaded by bootstrapping using '@angular/platform-browser-dynamic' or '@angular/platform-server',
or manually provide the compiler with 'import "@angular/compiler";' before bootstrapping.
Error: The NgModule 'BlockUIModule' needs to be compiled using the JIT compiler, but '@angular/compiler' is not available.

JIT compilation is discouraged for production use-cases! Consider using AOT mode instead.
Alternatively, the JIT compiler should be loaded by bootstrapping using '@angular/platform-browser-dynamic' or '@angular/platform-server',
or manually provide the compiler with 'import "@angular/compiler";' before bootstrapping.
at getCompilerFacade (core.mjs:5224:15)
at BlockUIModule.get (core.mjs:24815:34)
at getNgModuleDef (core.mjs:1951:29)
at verifySemanticsOfNgModuleDef (core.mjs:24904:23)
at BlockUIModule.get (core.mjs:24862:30)
at getInjectorDef (core.mjs:447:13)
at walkProviderTree (core.mjs:9016:18)
at core.mjs:9063:25
at core.mjs:5277:76
at Array.forEach (<anonymous>)
at resolvePromise (zone.js:1193:31)
at resolvePromise (zone.js:1147:17)
at zone.js:1260:17
at _ZoneDelegate.invokeTask (zone.js:402:31)
at core.mjs:27127:55
at AsyncStackTaggingZoneSpec.onInvokeTask (core.mjs:27127:36)
at _ZoneDelegate.invokeTask (zone.js:401:60)
at Object.onInvokeTask (core.mjs:27437:33)
at _ZoneDelegate.invokeTask (zone.js:401:60)
at Zone.runTask (zone.js:173:47)

[emera]

Managed to reproduce the issue when using a clean build after adding block ui v2023.6 .
Released a new version of BlockUI

[rienk]

Thanks, this has solved the problem!
I have created another ticket for another problem I encountered in the extra component package: https://support.servoy.com/browse/SVY-18552

[rienk]

Servoy 2023.09
var file = plugins.file.createFile('rapport_test.pdf');
file.getAbsolutePath()
"C:\WINDOWS\system32\rapport_test.pdf"

Servoy 2023.06
var file = plugins.file.createFile('rapport_test.pdf');
file.getAbsolutePath()
"C:\Users\Prodist\Desktop\Servoy\developer\rapport_test.pdf"

is this an on purpose change in 2023.09?

[jcompagner]

that is completely depending on what the "user.dir" variable is..

Never do that, you need to have full paths don't try to write in the user dir (those are on many systems read only)

I have no idea why that would be changed in this scenario.