Bruno, Nothing prevents you from doing exactly what you want to do. We: (a) offer a download (b) have documentation stating what CAS jars you need for each type of authentication (and then the POM says what the actual dependencies are) (c) rely on Maven internally and its what we recommend because this way you never have to worry about dependencies but its a Java project so you're free to do whatever you want.
I don't know why you keep thinking you *have* to use Maven or you *have* to grab the source: http://www.ja-sig.org/products/cas/downloads/index.html You can do exactly your steps that you want. Nothing stops you. You're on your own for locating the dependencies though. But everything else should work fine. Again, all it is is a Java application so any standard method applies for building a Java app. We happen to use Maven so that's what's there. If you're comfortable with Ant, you can easily add an Ant script. -Scott On Wed, Feb 11, 2009 at 12:41 PM, Bruno Melloni <[email protected] > wrote: > 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. > > > > I hope that helps. > > > > bruno > > > > > > > > *From:* Scott Battaglia [mailto:[email protected]] > *Sent:* Wednesday, February 11, 2009 10:37 AM > *To:* [email protected] > *Subject:* Re: [cas-user] Configuring CAS - need advice > > > > -- > > 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 > > > -- > 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 > > -- 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
