Richard S. Hall wrote:
Marcel Offermans wrote:
We are using a custom "main" class that bootstraps the framework and
installs the basic bundles (everything up to and including the
"management agent"). This leaves the system in a state similar to
what an initial provisioning implementation would do.
We wrap this "main" class in a runnable jar that sets up the
classpath to include the Felix jars.
The standard Main is overall pretty simplistic, but it does allow you
to specify the location of the config.properties file using a system
property, so it is always possible to have a production
config.properties file too that you select via a system property when
you run in production mode.
I'll try to get to it but I think what needs to be done here is ...
(1) For UNIX installations to write a custom init script instead of the
default one that is generated
by the installer plugin and have that set two things:
- the configuration file used should be set to production.properties
- the profile to be used must be set to "production" so the default
(debug mode based) profile is not
used with the shell bundles in it
(2) For Windows installations we need to modify the custom inno.iss file
to set the system properties
for the shell service so that ...
- the configuration file used should be set to production.properties
- the profile to be used must be set to "production" so the default
(debug mode based) profile is not
used with the shell bundles in it
So as you can see we need some environment property to be set for both
cases to do the same things. Now is
it possible that the profile can be chosen inside the
config.properties? If so then I do not need a second
property to select the profile.
Alex
