Developing against multiple servoy.properties files

[david]

Is there a way to start up developer against different servoy.properties files like we could do with Servoy 3 and earlier? I'm going a little crazy with all the Servoy installs I have going -- one for each set of database connections. Be much easier to manage with properties files in 1-3 Servoy installs. The only reason I'd need more than one Servoy install then is for running different configurations of beans/plugins.

[Harjo]

Hi David,

look here: http://forum.servoy.com/viewtopic.php?f ... 814#p72262

[Roberto Blasco]

Hi david.

What I do is to save all servoy.properties files I use in a folder.

i.e.
[+] my_servoy_properties

• servoy(erp).properties
• servoy(cms).properties
• servoy(stores).properties
• servoy(hospital).properties

Before starting the developer I change the servoy.properties by the one I need (Just when I want to change of project). So ecah project has his own workspace, resource and servoy.properties.

It's very important to do it before starting the developer to let servoy engage the file.

Best regards. Roberto.

[david]

Hi David,

look here: http://forum.servoy.com/viewtopic.php?f ... 814#p72262

How to set up on a Mac?

[david]

Ah k, gottit. Other thread helped a lot Harjo, thanks.

1- Duplicate the Servoy developer file and the servoy.properties file and give unique names
2- Right-click on Servoy developer file and select "Show package contents"
3- Open file "Contents/MacOS/servoy.ini"
4- Specify the duplicated properties file by adding to the bottom:

Code: Select all

-Dproperty-file=servoy_cms.properties

5- You can also specifically set the workspace to load with this instance by adding the path information (enter above the -vmargs line, not at the bottom of the file):

Code: Select all

-data
/Users/admin/workspace_cms

The end result is multiple Servoy developer application icons -- each of which opens its own database connections and workspace. You can even run them simultaneously but I'm not sure how this would affect Eclipse history and other things that Eclipse stores to track your work session. I'm guessing things could get a little screwy