I created a step by step guide in a PowerPoint presentation with notes pages available in the CAS User Manual in the Wiki under Development. Get to it directly as:
http://www.ja-sig.org/wiki/download/attachments/10650489/Developing+in+CAS.p pt It shows how to check out a CAS 3.x release in Eclipse (MyEclipse or vanilla Ganymede) and develop new code, although I suppose you could just use it to configure. While this allows both Eclipse and Maven deployment in parallel, you keep two separate WAR directories for the two build environments and have to manually copy changes from one webapp directory to the other. This reflects what I regard as a high probability that you will have two different configurations for rough development and debugging (Eclipse) and then for integration testing (Maven). The Powerpoint is one release of MyEclipse behind, and the details of how a Maven project looks after it has been imported into MyEclipse seems to change slightly across releases. More importantly, MyEclipse 7 comes with a strong bias to use Pulse, a really neat catalog of third party Eclipse pugins you can add almost seamlessly) which will be a really good tool if they ever get it to run reliably. So while the PPT goes to a lot of trouble to tell you how to find and install the Subversive plugin manually, with Pulse you just select Subversion from the catalog and it gets installed. Unfortunately, a few weeks later Pulse corrupts itself and you cannot install or update anything new and have to start over from scratch, or maybe I just haven't mastered it. The notes pages explain what each step is doing and the "philosophical" differences between Maven, MyEclipse, and vanilla Ganymede WTP, so if you hit a small difference you should be able to navigate around it or just ask the list. From: Bruno Melloni [mailto:[email protected]] Sent: Wednesday, February 11, 2009 12:42 PM To: [email protected] Subject: RE: [cas-user] Configuring CAS - need advice Thank you Scott for your reply. It doesn't look like I am going to be successful at configuring CAS, primarily because of its documentation. Which is frustrating, since it is obviously a very flexible and complete project - just hard to use. But I'd like to make a suggestion that should help make it an easy to use product. It will be too late for me, but it should benefit others. Free those trying to simply 'use' CAS from special builds. It shouldn't be necessary to build from source or even rely on Maven. The steps could be something as simple as: (a) Download CAS. (b) Grab a base WAR (or EAR) similar to the sample WAR currently included (possibly the current sample WAR?). (c) Import it into the user's development environment of their choice (Eclipse, RAD, Netbeans, IntelliJ, whatever). (d) Add a provider JAR into WEB-INF/lib for the type of provider they plan to use. (e) Modify deployerConfigContext.xml for the particular provider. (f) Modify the JSPs to match the user's desired look and feel. (g) Use the development environment to build and deploy the WAR/EAR. And simple step by step instructions on how to do the above, without assuming any prior knowledge should make it possible for users of any background to consistently configure and deploy CAS. -- 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-user
