Problem: The lookup strategy for configuration is hard-coded into the filter, making it impossible to replace or expand. Solution: Pull the strategies into their own classees and make it configurable. Default to the previous strategy. QA Notes: The current unit tests work. New unit tests for the configuration will have to be added once the design is approved. |
||
|---|---|---|
| cas-client-core | ||
| cas-client-integration-atlassian | ||
| cas-client-integration-jboss | ||
| cas-client-integration-tomcat-common | ||
| cas-client-integration-tomcat-v6 | ||
| cas-client-integration-tomcat-v7 | ||
| cas-client-support-distributed-ehcache | ||
| cas-client-support-distributed-memcached | ||
| src/licensing | ||
| .gitignore | ||
| LICENSE | ||
| NOTICE | ||
| README.txt | ||
| assembly.xml | ||
| pom.xml | ||
README.txt
BUILDING THE CAS CLIENT FOR JAVA Please note that to be deployed in Maven Central, we mark a number of JARs as provided (related to JBoss and Memcache Clients). In order to build the clients, you must enable the commented out repositories in the appropriate pom.xml files in the modules (cas-client-integration-jboss and cas-client-support-distributed-memcached) or follow the instructions on how to install the file manually.