Page Comparison

...

1. Full build

   No Format
   mvn clean install

2. Generate the local configuration file configured with default values

   No Format
   mvn generate-resources -Plocal

   1. The above command generates the file

      No Format
      ~/.kuali/ole/fs/configuration.properties

3. Package OLE FS data into jar files

   No Format
   mvn clean install -Pdata

4. Reset an OLE FS database

   No Format
   mvn clean initialize -Pdb

Property Loading

1. Runtime property resolution is now possible for OLE FS!
2. This means the exact same war file can be used for development as well as deployment without altering the binary
3. Automatically loaded external configuration files are used to reconfigure the binary with machine specific configuration
4. The default external directory used by OLE FS is now based on the system property user.home
5. To change this you only have to override one property - ole.fs.home
   1. Properties pointing to other directories needed by OLE FS are expanded into their absolute path at runtime
   2. This way only a single property needs to be overridden (instead of all of them)
6. The following external property locations are automatically checked and loaded, in this order, if they exist

   1. No Format
      ~/.kuali/ole/fs/configuration.properties

   2. If the system property olefs.configuration is set, the properties file it points to is automatically loaded
7. If the property ole.fs.runtime.property.expansion=true the following actions are also taken
   1. After loading classpath:configuration.properties load classpath:olefs-default.properties
   2. Expand any properties containing placeholders into their fully resolved equivalents

...