The WAR Overlay method (uber-webapp) was the preferred way to operate, and it is still useful to isolate local changes from the base code. That said, it should never have been inside the cas-server project proper because it should not generate a formal artifact. I suggest neither dropping it nor deprecating it, but rather moving it to an external example status where it documents the technique for WAR Overlay without being part of the mainstream build. You could do the same thing with JBoss, where it has been retired as supported code but is still available as an example of an alternative TicketRegistry.
Uber-webapp is at best a starting point. It is useless if you don’t add your own stuff, and you don’t get very far before you are customizing even the Build section of the POM to exclude JAR files and so on. Instead of one official version of the thing, it would be more useful if there were alternates for various target configurations (JBoss EAP 6, Tomcat 8, Glassfish, …) that people could contribute. That suggests that it is a sample and not part of the release. From: Scott Battaglia [mailto:[email protected]] Sent: Wednesday, May 21, 2014 7:38 AM To: [email protected] Subject: Re: [cas-dev] CAS 4.1.0 I'm not really sure we can just drop something without deprecating it first. -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
