...
We recommend building and running KFS locally. The KFS war can be build using maven (
mvn -DskipTests=true package) and deployed to a container such as Tomcat.Info Note, the -DskipTests=true is optional, but if you don't skip the tests, they will take some time to run and aren't strictly necessary for packaging the KFS war.
- We recommend building and running a Standalone Rice instance locally. The Rice war can also be built using maven and deployed to a container such as Tomcat. See the Rice Documentation. Also, see Development Standalone Rice for information on setting up your database and standalone rice on your workstation.
To enable optional modules we need to toggle the module.<module name>.enabled property to true, add the appropriate spring files, and add message property files. Take care to add sec files to the current properties particularly for property.files and rice.struts.message.resources. For example, to enable Access Security:
Code Block module.access.security.enabled=true fin.kr.additionalSpringFiles=[CURRENT fin.kr.additionalSpringFiles],\ classpath:org/kuali/kfs/sec/spring-sec-rice-overrides.xml institution.spring.source.files=,\ classpath:org/kuali/kfs/sec/spring-sec.xml,\ classpath:org/kuali/kfs/sec/spring-sec-gl-overrides.xml,\ classpath:org/kuali/kfs/module/ld/spring-sec-ld-overrides.xml,\ classpath:org/kuali/kfs/module/purap/spring-sec-purap-overrides.xml property.files=[CURRENT property.files],classpath:org/kuali/kfs/sec/sec-resources.properties rice.struts.message.resources=[CURRENT property.files],org.kuali.kfs.sec.sec-resources
...