John, CAS 3.2.1 (and possibly CAS 3.1.1, but I can't recall immediately) all use Maven2 for their build management. This doesn't preclude you from doing any plugins, but it allows you to create your plugins as standard Maven2 projects outside of the CAS project, to ensure a cleaner separation of local concerns and the 3rd party product.
We have some basic documentation on using CAS with the Maven WAR Overlay plugin which essentially allows you to develop locally and then include the prebuilt CAS war file, overriding files where necessary (and including new ones). http://www.ja-sig.org/wiki/display/CASUM/Building+and+Deploying There is an example with the Maven overlay though it doesn't do it as a separate project (which is actually the way it should be done). -Scott On Thu, Jun 5, 2008 at 12:28 PM, John M Stewart <[EMAIL PROTECTED]> wrote: > > Hello, > > I'm having issues trying to develop a localPlugin to modify the login > web-flow using CAS server 3.1.1. It seems that the distribution doesn't > include the spring-ldap jar necessary for the build. I've searched > through the entire 3.1.1 dist and I can't find the spring-ldap jar. > > Also I'd like to work with the 3.2.1 distribution to add support for > password change/expiration but it doesn't seem that plugins are supported > in 3.2.1 anymore. I can't find any reference to localPlugin or an ant > script to build with. Can anyone assist me or point me in the right > direction here? Thanks for your help! > > John. > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas > -- -Scott Battaglia PGP Public Key Id: 0x383733AA LinkedIn: http://www.linkedin.com/in/scottbattaglia
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
