Mike Thanks for the information. If you find anything interesting, please let us know. I believe a couple of our jars may be pulled in merely because one of our dependencies has a weird dependency relationship (i.e. antlr?). We're also always interested in ways that the core can be split into further modules (i.e. possibly a Google Accounts module).
Thanks -Scott On Mon, Apr 7, 2008 at 1:21 PM, Mike McEwan <[EMAIL PROTECTED]> wrote: > Scott, Thanks for the response. > > I'll maybe try starting a new maven project from scratch with > 'cas-server-core' and the basic spring stuff then build it up from there. I > found a very useful utility - 'loosejars' from Google Code. It basically > reports on the number of classes loaded from a given jar and can report as > an application executes. I noticed another post that mentions that some > dependency analysis needs to be conducted on the 'cas-server-webapp' before > it could be placed in a public maven repo - perhaps 'loosejars' could help > here? > > Anyway, thanks again for the response. > > -- > Mike. > > On 7 Apr 2008, at 02:35, Scott Battaglia wrote: > > Mike, > > You could pare things down a bit by removing some jars but it won't make > it any more lightweight (other than taking up slightly less room on the hard > drive). > > However, if you must remove some jars, you can try removing the following > (I can't guarantee what will work after these are removed): > * The AspectJ items if you aren't using the Inspektr tool > * Acegi and cas-client if you aren't using the Services Management tool > (may require certain configuration to be removed) > * The XML and digital signature stuff if you aren't using Google Accounts > support > * OpenSAML if you aren't using the SAML support > > There may be more but I don't have the list handy. > > -Scott > > On Sat, Apr 5, 2008 at 6:02 AM, Mike McEwan <[EMAIL PROTECTED]> > wrote: > > > Hi, > > I've been looking at CAS as an alternative to Tomcat's single > > sign-on filter. CAS looks like a a good way of removing the container > > dependencies of my current single sign-on solution allowing me to drop > > my applications into an alternative app server's deployment directory > > if I so wish. However, looking at the default 'cas-server-webapp', I > > see it weighs in at around 9MB with all the dependencies it packages. > > This seems a little over the top for my simple requirements and so I > > was wondering if I could pare things down a bit? > > > > For example, I will not be using either LDAP or a database - does this > > mean I can remove the Spring jars that support these? is the aspectj > > weaver jar really required at run time? I appreciate that CAS is an > > 'enterprise' solution that supports a variety of 'backends' out of the > > box, but I would appreciate any help/advice in slimming it down for my > > simple use case. > > > > -- > > Mike. > > > > _______________________________________________ > > 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 > > > > _______________________________________________ > 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
