AW: Maintaing local customizations via Maven2

[Scott Battaglia]

Matt,

Would be a good first step be to move the changes in 1 and 3 to
deployerConfigContext.xml (or at least #3, and we could move the themename
to the cas.properties file).

We should also look into a ViewsResolver that can maybe read views from a
JAR file so people can merely include the JAR file with the JSP pages and
the properties files.

-Scott



On 8/27/07, Smith, Matt <matt.smith at uconn.edu> wrote:
>
>
> ...
> >  A second step could be to identify commonly changed items in the XML
> > files and isolate those changes to one file so that merging becomes
> > easier.
> ...
>
>
> Not sure how common my changes are, but:
>
> 1) I change cas-servlet.xml to reflect my "ThemeName" and "basename".
> 2) I change deployerConfigContext.xml to reflect my
> authenticationHandler.
> 3) I change securityContext.xml to remove "battags" from "ROLE_ADMIN",
> and eventually will be replacing the inMemoryDaoImpl with something
> better.
> 4) I include my view pages in views/jsp/uconn
> 5) I include my themes in themes/uconn
> 6) I modify the log4j.properties in WEB-INF/classes
> 7) I add a uconn.properties and a uconn_views.properties to
> WEB-INF/classes.
>
> If the XML changes in 1-3 could be centralized, it would help.
>
> I'll post something (to the Wiki if appropriate) about managing these
> customizations as a Maven project, once I actually hammer out the
> details.
>
> HTH,
> -Matt
>
> --
> Matt Smith
> matt.smith at uconn.edu
> University Information Technology Services (UITS)
> University of Connecticut
> PGP Public Key: http://web.uconn.edu/dotmatt/matt.asc
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
>


-- 
-Scott Battaglia

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