Sorry

I forgot to paste the link here.

Here you are.
http://www.ja-sig.org/wiki/display/CASUM/Maintaining+local+customizations+using+Maven+2

Harry


BigEHokie wrote:
> 
> I can't find it on the wiki....where is it?
> 
> 
> Harry Ng wrote:
>> Hi all,
>> 
>> I have currently created a page on wiki, which we can put the suggestions
>> on
>> this topic. Please help to document what you did and what problems you
>> tackled in using Maven 2 for your local customizations.
>> 
>> Thanks and Regards,
>> Harry
>> 
>> 
>> BigEHokie wrote:
>>> On 9/27/07, Eric Miles <[EMAIL PROTECTED]> wrote:
>>>
>>>     I'm assuming when you're talking about declaring the original cas
>>> webapp
>>>     as a dependency you are talking about doing a maven2 web application
>>>     overlay, correct?  If so, I HIGHLY second this notion.
>>>
>>>     However, if you are not...
>>>
>>>     I HIGHLY recommend it :)  Doing webapp overlays with Maven2 makes
>>>     extending and customizing web applications SUPER easy.  The only
>>> problem
>>>     I see with the CAS in its current form is the fact that Maven2 will
>>> not
>>>     install the cas.war file into the local repository due to naming.  I
>>>     think it has to be named in an artifactId-version.type fashion.  You
>>> can
>>>     get around this by installing it manually with
>>>     install:install-file....However the cleaner and more Maven2 solution
>>>     would be to let the Maven2 and the POM do the work itself.
>>>
>> 
>> 
>> Smith, Matt 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
>>> [EMAIL PROTECTED]
>>> University Information Technology Services (UITS)
>>> University of Connecticut
>>> PGP Public Key: http://web.uconn.edu/dotmatt/matt.asc
>>>
>>>  
>>> _______________________________________________
>>> 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
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Maintaing-local-customizations-via-Maven2-tf4311564.html#a13031153
Sent from the CAS Users mailing list archive at Nabble.com.

_______________________________________________
Yale CAS mailing list
[email protected]
http://tp.its.yale.edu/mailman/listinfo/cas

Reply via email to