Page Comparison

...

1. ${user.home}/ole-build.properties

   Info
   User Home Locations Unix: /home/username/ole-build.properties Mac OS X: /Users/username/ole-build.properties Windows XP: C:/Documents and Settings/username/ole-build.properties Windows Vista: C:/Users/username/ole-build.properties

2. ${institution.build.properties.file} (location set in the above ole-build.properties)
3. ${build.environment}-build.properties
4. The build/properties directory in the ole project. You should not generally change the properties here. Override them in one of the above files.
   • build/properties/build.properties
   • build/properties/database.properties
   • build/properties/directory.properties
   • build/properties/logging.properties
   • build/properties/batch.properties
   • build/properties/email.properties
   • build/properties/url.properties
   • build/properties/cas.properties
   • build/properties/rice.properties
   • build/properties/spring.properties
   • build/properties/web.properties
   • build/properties/b2b.properties

For ease of future upgrades, you should avoid modifying any of the delivered files under the ole directory. Instead, you can override any or all of those properties in the first two. For example...

1. Create a second build properties file in the root of the project (e.g. sampleu-build.properties).
2. Ensure that your new properties file will be loaded by adding the following to your ${user.home}/ole-build.properties file.

   Code Block
   title example institution properties reference
   institution.build.properties.file=sampleu-build.properties

Build Target Overview

To deploy OLE, you can use the dist or dist-local targets of the OLE build.xml. To execute the OLE unit tests, you can use the test-local or continuous-integration targets.  The dist-local and test-local targets assume that you are using an IDE for compilation. If not, you will need to add this line to your build properties file and use the make-source target, too: war.classes.directory=work/web-root/WEB-INF/classes. The continuous-integration target is intended for use within an automated testing tool like Hudson. See the setup instructions and the help target in the build file itself for more information.

...