[cas-dev] CAS Client Dependencies on CAS Core

[Scott Battaglia]

I don't think its worth the effort to maintain two different jars for core
CAS Server code nor are there enough classes to create a separate project.
The CAS Server JAR is relatively small and the unused classes have no affect
on the client. This may be something to revisit at a later time though.

Newer versions of the CAS client (i.e. HEAD :-)) also depend on classes not
in the principal package.

-Scott

On 3/1/07, Marvin S. Addison <serac at vt.edu> wrote:
>
> In browsing the CAS client source, it was clear that very little of the
> CAS core library, which is distributed with the client, is used by the
> client.  The 3.1-m1 client depends on the following classes:
>
> org.jasig.cas.authentication.principal.Principal
> org.jasig.cas.authentication.principal.SimplePrincipal
> org.jasig.cas.authentication.principal.Service
> org.jasig.cas.authentication.principal.SimpleService
> org.jasig.cas.authentication.principal.AttributePrincipal
> org.jasig.cas.authentication.principal.SimpleAttributePrincipal
>
> Since everything in the client depends solely on classes in the
> principal package, it seems straightforward to separate this out into a
> separate target, e.g. cas-common.jar.  Thoughts?
>
> Regards,
> Marvin Addison
> --
> Applications Programming Analyst
> Collaborative Technologies Unit
> Virginia Tech
>
>
> _______________________________________________
> cas-dev mailing list
> cas-dev at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas-dev
>



-- 
-Scott Battaglia

LinkedIn: http://www.linkedin.com/in/scottbattaglia
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas-dev/attachments/20070305/be3fa9a4/attachment.html