2.2.1 changes location os servoy.properties

Classic Servoy
1

Running Servoy on linux… with servoy installed by one user in /usr/local/servoy but run by a different user…

With all versions up to 2.2(final) on startup Servoy looked for $HOME/servoy.properties

After upgrading to 2.2.1 Servoy looks for $INSTALLDIR/servoy.properties (or is it the -Duser.dir=/usr/local/servoy ?) :-(

Was this supposed to change?

Thanks,
Neale.

2

Yes MANY did not understand that servoy was able to use the user dir. when the install dir was write protected, so we stopped supporting this.

3

Jan Blok:
Yes MANY did not understand that servoy was able to use the user dir. when the install dir was write protected,

Initially I couldn’t make sense of this, except now if I read s/user dir/home dir/

Jan Blok:
so we stopped supporting this.

But this means the upgrade 2.2 → 2.2.1 breaks a working installation, in the case where the install dir is not writable by the user running Servoy and so the servoy.properties is in $HOME :-(

Any chance of backing out this change?

Also, with respect to this, am I doing the right thing by including -Duser.dir=/usr/local/servoy in the command to run servoy?

Thanks,
Neale.

4

Neale:
But this means the upgrade 2.2 → 2.2.1 breaks a working installation, in the case where the install dir is not writable by the user running Servoy and so the servoy.properties is in $HOME :-(

Well it only applies for the Servoy Application server, what is the problem making the app server dir writeable?

5

No, my comments are with respect to Developer.

Are you telling me that Developer and App Server differ in their behaviour re the location of servoy.properties? That would be scary :-(

Regards,
Neale.

6

Its also developer (but for developer it’s not really a problem I guess?)

7

Developer is where I got the initial “surprise”. It worked just fine with the install directory being read-only for the user running Servoy - until 2.2.1.

Why should the user running servoy need write access to the software install directory? FWIW, I see that question being like “why should a regular user have write access to /bin?”.

Regards,
Neale (who really must go and get some sleep now ;-)

8

Neale:
“why should a regular user have write access to /bin?”.

Well I agree, it should not be required, but windows/mac users did not get the idea (and we got almost every week questions about it) so we stopped supporting this.

9

That’s really sad.

Any reason I shouldn’t be able to work around this breakage with -Dproperty-file=${HOME}/servoy.properties in the command line invocation?

Thanks,
Neale.