| Warning | ||
|---|---|---|
| ||
CAS documentation has moved over to apereo.github.io/cas, starting with CAS version 4.x. The wiki will no longer be maintained. For the most recent version of the documentation, please refer to the aforementioned link. |
As of CAS 3.1, CAS builds exclusively with the Maven 2 Build Management System. This system provides a common build and directory structure across all projects that use Maven 2 and defines common goals that can be applied to any project type (JAR, WAR, EAR, etc.).
Building CAS
In your CAS_HOME, you can type "mvn package install". This will create all of the jar and war files for the CAS modules. Alternatively, you can enter any of the CAS_HOME/{module} sub directories and execute "mvn package install" to generate just that particular JAR or WAR.
As compilation require requires a network connection, if you are behind a http proxy, you have to indicate some extra option to mvn command: "mvn -Dhttp.proxyHost=xxx -Dhttp.proxyPort=xxx package install"
...
Once you've configured CAS, you can run "mvn package" to generate the WAR file.
...
WAR Overlay
Deployers do concern concerned about the management of local customizations , upon CAS 3.1.1, Maven 2 has been employed as the major management tool in the project. It is suggested Maven can also offer a help in maintaining local customizations. Here is a page for the detailscan use the Maven2 WAR Overlay method for keeping their local changes separate from the main distribution. Details on that can be found here.