Andrew, On Fri, May 23, 2008 at 10:23 AM, Andrew R Feller <[EMAIL PROTECTED]> wrote:
> <snip /> > > > > > - Web interface for configuring CAS; our technical support group that > maintains services doesn't have time to be Spring savvy > - Federation; I know Shibboleth has been out for a while and we are > starting to hear people requesting some way of hooking into their > federations > - Administration summary views; this is a huge deal for us as our > technical support guys have over a hundred virtual servers to manage > - Improved clustering support; clustering performance and configuration > for unicasting are big for us as we dealing with random out of memory > exceptions > > I added LSU as "interested" in these features. Appearing as "interested" is not an obligation to implement any of these features (but hey if you want too... ;-)) it just helps us keep track of priorities. > > > The only new feature request I can throw out there is a non-Maven process > for customizing CAS. We are in the process of working out our Java > continuous integration / deployment process, however I can tell you that > Maven isn't in the picture. As a temporary band-aid, I developed a small > time system of my own that contains a minimal POM that builds CAS with the > necessary subprojects we need (core, webapp, jboss, ldap) from JA-SIG's > repository and an Ant script that overwrites the contents of the WAR with > default customizations such as themes and CAS configurations that are not > machine specific and then machine specific customizations. Once all of this > is done, it is re-WARed and can be dropped into a Tomcat instance. The nice > thing is that this process is nothing but a bunch of folders with CAS files > and three bui > I can state that as of right now I don't envision the CAS project using anything other than Maven for its own internal build system, and we'll continue to support people who use the WAR overlay method. That said, we would continue to strive to make improvements to the process to support other methods. For example, you should be able to use a combination of Ant+Ivy to pull in the dependencies from any Maven repository. Feel free to add something about "Ensuring support for non-Maven2 end-user builds" if you'd like. > > > As for my personal commitment, I realize I have been slack on the > documentation efforts due to the burden of constant projects. I think it > would be beneficial to have documentation that shows people how to properly > setup Tomcat for SSL. I know that is not the point of CAS documentation, > however we should atleast keep links to external documentation that does > because it seems to be a hurdle for most people new to Tomcat administration > as I was a year ago. Honestly, I am still frustrated by keystores, which is > why I have settled on using APR for SSL. I would be glad to write up on how > to compile and setup APR for Tomcat at the very least and even using Apache > HTTP in front of Tomcat. > If you get a chance that would be great! We don't turn down documentation help ;-) Thanks -Scott > > > Thanks for all of the good work! > > > > Andrew R Feller, Analyst > > University Information Systems > > 200 Fred Frey Building > > Louisiana State University <http://www.lsu.edu/> > > Baton Rouge, LA, 70803 > > (225) 578-3737 (Office) > > (225) 578-6400 (Fax) > > > ------------------------------ > > *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On > Behalf Of *Scott Battaglia > *Sent:* Friday, May 23, 2008 8:36 AM > *To:* CAS Developers Mailing List; CAS Users Mailing List; > [EMAIL PROTECTED] > *Subject:* CAS Vision and Roadmap > > > > All, > > I've taken Ben's initial CAS 4 roadmap document, the wish list, and some > use cases that I had been keeping track of that you guys had mentioned on > the mailing list as well as my own "view" of the CAS 3 and potential CAS 4 > projects and pulled that all into one document entitled "CAS Vision and > Roadmap (All Versions)": > > http://www.ja-sig.org/wiki/display/CAS/CAS+Vision+and+Roadmap > > I'd like to encourage people to add their own ideas. What I had been > trying to do was for the CAS 3.x branch, entries could be more specific due > to the fact that the software already exists, but for the CAS 4.x branch, a > lot of the ideas are more abstract due to the fact that the product doesn't > exist. If you're interested in one of the items that are already there, > please feel free to add your institutions/organization/company/individual > name (especially if you're willing to help ;-)) Knowing who is interested > and who can help allows us to prioritize features and ideas around those > that are most likely to be used and actually implemented. > > Note that if you were at the recent JASIG conference (I unfortunately > couldn't be due to an exam), you probably saw some of the JASIG members > talking to the Internet2 Middleware team during the BarCamp portion of the > conference. This roadmap and vision does include anything that may have > come out of that initial meeting but will be continually updated when/if > anything evolves from those discussions. > > Also, please note that no secret work has begun on a CAS 4 project. There > is no warranty implied by the linked document. If the community sees no > need for a CAS4 then there would be no CAS 4 ;-) > > And I'm sure sending this out on the Friday before a U.S. holiday weekend > probably wasn't the best time, but I'm hoping you will all see it and > participate! > > Have a good weekend (3-day weekend for those in the U.S. ;-)) > > -Scott > -- > -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 > > -- -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
