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 -- Matthew J. Smith <[EMAIL PROTECTED]> University of Connecticut UITS This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
