...
| Panel |
|---|
Note that Spin's approach is not very fine-grained. If two files with the same name are present in $SPIN_HOME/conf and on the classpath, the one from $SPIN_HOME/conf will "win", and ONLY values from the winning file will be used. It is NOT the case that data from two or more config files will be superimposed on each other, or merged in any way. |
| Panel |
How $SPIN_HOME is determined
$SPIN_HOME is determined in the following way:
If the SPIN_HOME JVM system property is set, its value is used for $SPIN_HOME.
If the SPIN_HOME environment variable is set, its value is used for $SPIN_HOME.
| Panel |
|---|
Note that if the SPIN_HOME JVM system property and environment variable are both set, the value of the JVM system property "wins". |
If neither the SPIN_HOME JVM system property nor environment variable are set, $SPIN_HOME is formed by appending the current user's home directory with '.spin', or 'spin' on Windows.
The class org.spin.tools.config.Environment expresses these rules.