...
- Determine what version of KFS you want to work with.
- Create a separate Eclipse project in your local version control for your customizations (see #Eclipse Setup).
- Set the following property in the kfs-build.properties file in your user home directory to load an institution build properties file that will facilitate a build time merge of the delivered code and your customizations.
# supply the path to a build properties file in the project containing your customizations (tip: use a relative reference)
institution.build.properties.file= - Set the following in your institution build properties file as needed.
# add configuration properties for your implementation (this file will be tokenized along with its delivered counterpart)
institution.configuration.properties.file=
# pull new or replacement files into the external security directory
institution.security.directory=
# add secure properties for your implementation (this file will be tokenized along with its delivered counterpart)
institution.security.properties.file=
# add logging properties for your implementation (this file will be tokenized along with its delivered counterpart)
institution.log4j.properties.file=
# pull new or replacement files into the application server used for development
institution.appserver.directory=
# create additional directories in and pull new or replacement files into the staging and reports directories
institution.work.directory=
# merge implementation java, xml and property source files into the delivered code for war builds
institution.source.directory=
# merge implementation web content into the delivered code for war builds
institution.web.content.directory=
# merge implementation test source files into the delivered test suite for automated execution
institution.test.source.directory=
# merge implementation libraries into the delivered library
institution.lib.directory= - Set other build properties in your implementation properties file to load implementation Spring, OJB, Struts, etc. files that will override and supplement the behavior of the delivered application (also see KFS Customizations.
Choose the appropriate location for the files that you add in order to override or extend delivered functionality.
Note To make things simpler for your developers, we suggest following the structure of the delivered project and simply replacing org.kuali.kfs with an appropriate value for your institution in package names.
- Determine how you will obtain KFS from the Foundation repository for test, training, and production server deployments, if you want to automate those (see #Server Builds).
...