Generic CAS Gradle war overlay to exercise the latest versions of CAS. This overlay could be freely used as a starting template for local CAS Gradle war overlays.

• CAS 5.3.x

• JDK 1.8+

The etc directory contains the configuration files that are copied to /etc/cas/config automatically.

CAS modules may be specified under the dependencies block of the CAS subproject:

dependencies {
    compile "org.apereo.cas:cas-server-webapp-tomcat:${project.'cas.version'}@war"
    compile "org.apereo.cas:cas-server-some-module:${project.'cas.version'}"
    ...
}

Study material:

• https://docs.gradle.org/current/userguide/artifact_dependencies_tutorial.html
• https://docs.gradle.org/current/userguide/dependency_management.html

To see what commands are available to the build script, run:

./build.sh help

To package the final web application, run:

./build.sh package

To update SNAPSHOT versions run:

./build.sh package --refresh-dependencies

If you need to, on Linux/Unix systems, you can delete all the existing artifacts (artifacts and metadata) Gradle has downloaded using:

# Only do this when absolutely necessary!
rm -rf $HOME/.gradle/caches/

Same strategy applies to Windows too, provided you switch $HOME to its equivalent in the above command.

To see what commands are available in the build, use:

 ./gradlew[.bat] tasks

To see where certain dependencies come from in the build:

# Show the surrounding 2 before/after lines once a match is found
 ./gradlew[.bat] allDependencies | grep -A 2 -B 2 xyz

Or:

./gradlew[.bat] allDependenciesInsight --configuration [compile|runtime] --dependency xyz

• Create a keystore file thekeystore under /etc/cas on Linux. Use c:/etc/cas on Windows.
• Use the password changeit for both the keystore and the key/certificate entries.
• Ensure the keystore is loaded up with keys and certificates of the server, by adding the following to ./etc/cas/config/cas.properties:

server.ssl.keyStore=file:/etc/cas/thekeystore
server.ssl.keyStorePassword=changeit
server.ssl.keyPassword=changeit

On a successful deployment via the following methods, CAS will be available at:

• http://cas.server.name:8080/cas
• https://cas.server.name:8443/cas

Run the CAS web application as an executable WAR.

./build.sh run

Run the CAS web application as an executable WAR via Spring Boot. This is most useful during development and testing.

./build.sh bootrun

Be careful with this method of deployment. bootRun is not designed to work with already executable WAR artifacts such that CAS server web application. YMMV. Today, uses of this mode ONLY work when there is NO OTHER dependency added to the build script and the cas-server-webapp is the only present module. See this issue for more info.

Deploy resultant cas/build/libs/cas.war to a servlet container of choice.

You can also run the CAS server in DEBUG mode to step into the code via an IDE that is able to connect to the port 5005.

./build.sh debug

To setup a development environment for either eclipse or IDEA:

# ./gradlew[.bat] eclipse
# ./gradlew[.bat] idea

The above tasks help to setup a project for your development environment. If you find that something has gone wrong, you can always start anew by using the following:

# ./gradlew[.bat] cleanEclipse
# ./gradlew[.bat] cleanIdea

You may explode/unzip the generated CAS web application if you wish to peek into the artifact to examine dependencies, configuration files and such that are merged as part of the overlay build process.

./gradlew[.bat] explodeWar

Invokes the CAS Command Line Shell. For a list of commands either use no arguments or use -h. To enter the interactive shell use -sh.

./build.sh cli