I simply integrated CAS in other web application. I recently moved from 3.0.7 to 3.1, and it was almost painless - it took 1 hour aprox.
I followed what eric suggests: building a new maven war that depends on cas jars. This war includes all the spring configuraiton, my customizations and additional sources. Regards Eric Miles wrote: > I'm assuming when you're talking about declaring the original cas webapp > as a dependency you are talking about doing a maven2 web application > overlay, correct? If so, I HIGHLY second this notion. > > However, if you are not... > > I HIGHLY recommend it :) Doing webapp overlays with Maven2 makes > extending and customizing web applications SUPER easy. The only problem > I see with the CAS in its current form is the fact that Maven2 will not > install the cas.war file into the local repository due to naming. I > think it has to be named in an artifactId-version.type fashion. You can > get around this by installing it manually with > install:install-file....However the cleaner and more Maven2 solution > would be to let the Maven2 and the POM do the work itself. > > Eric > > Hausherr, Jens wrote: >> Hi Matt, >> >> I found two options for maintaining the CAS webapp as a maven 2 project: >> >> 1) create a maven project and simply copy the sources of the CAS Webapp into >> the project. Works but is prone to be painful on an upgrade of CAS... >> >> 2) Create your own webapp and declare the original CAS webapp as an >> dependency. Works quite nicely if you do not have to customize any files of >> the original webapp. >> >> I have benn using version 1 but would try to migrate to vesion 2 in the near >> future... >> >> Regards, >> Jens >> >> -----Ursprüngliche Nachricht----- >> Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Smith, Matt >> Gesendet: Donnerstag, 23. August 2007 14:01 >> An: Yale CAS mailing list >> Betreff: Re: Maintaing local customizations via Maven2 >> >> Based on the lack of responses, I'm going to guess that few, if any, >> have turned their customizations into a local maven project. So then, >> let me ask a different question -- are most of you maintaining your >> customizations (choice of authentication handlers, page design, flow) by >> hand? Is your upgrade/modification process to apply these changes by >> hand each time, following some local documentation? >> >> My goal is to have a reproducible build that creates our local >> customized war bundle, maintains our dependencies on external libraries >> (e.g., the JAAS modules we require), and can be largely re-used by our >> team for new modifications or upgrades. Any thoughts on how to >> accomplish this? >> >> >> On Wed, 2007-08-22 at 08:58 -0400, Smith, Matt wrote: >>> I'm looking for suggestions on the most appropriate way to maintain my >>> local CAS server customizations, ideally as a Maven project. I see two >>> options: >>> >>> 1) Create a new Maven "uconn-sso" project, with a dependency on >>> cas-server-webapp (war). Include in my project my custom web pages and >>> config files that should override those in cas-server-webapp. >>> >>> 2) Copy cas-server-webapp to my own "uconn-sso" project. Make >>> modifications directly to this project. >>> >>> I'm wondering if anyone has any thoughts on which process is "better", >>> or if there are options I have not yet considered. By "better", I am >>> looking for ease of new customizations, and ease of upgrade transitions. >>> >>> Any thoughts are appreciated. Thanks, >>> -Matt >>> >>> _______________________________________________ >>> Yale CAS mailing list >>> [email protected] >>> http://tp.its.yale.edu/mailman/listinfo/cas > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas -- Pablo Gra\~na Chief Architect Globant Arg Office: +54 (11) 4109 1743 UK Office: +44 (20) 7043 8269 int 8043 US Office: +1 (212) 400 7686 int 8043 _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
