oodt-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Laidlaw (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OODT-650) Remove duplicate context container from CAS-Product web application
Date Wed, 07 Aug 2013 22:26:49 GMT

     [ https://issues.apache.org/jira/browse/OODT-650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Ross Laidlaw resolved OODT-650.
-------------------------------

    Resolution: Fixed
    
> Remove duplicate context container from CAS-Product web application
> -------------------------------------------------------------------
>
>                 Key: OODT-650
>                 URL: https://issues.apache.org/jira/browse/OODT-650
>             Project: OODT
>          Issue Type: Task
>          Components: product server
>    Affects Versions: 0.7
>            Reporter: Ross Laidlaw
>            Assignee: Ross Laidlaw
>            Priority: Trivial
>              Labels: gsoc
>             Fix For: 0.7
>
>         Attachments: OODT-650.rlaidlaw.2013-08-05.patch.txt
>
>
> The CAS-Product web application has two examples of Tomcat context containers.  The first
example 'cas-product-tomcat-5.5.9.xml' is in src/main/resources, and the second example 'context.xml'
is in src/main/webapp/META-INF.
> When building the webapp, both files are copied into the same META-INF directory in the
target WAR.  The context.xml file is copied by default and the cas-product-tomcat-5.5.9.xml
file is copied by the following maven-war-plugin configuration in the POM:
> {code:xml}
> <containerConfigXML>
>   src/main/resources/cas-product-tomcat-5.5.9.xml
> </containerConfigXML>
> {code}
> So we end up with two almost identical context container files in META-INF:
> {noformat}
> META-INF
> - cas-product-tomcat-5.5.9.xml
> - context.xml
> {noformat}
> I was thinking that we could remove cas-product-tomcat-5.5.9.xml from src/main/resources
and keep src/main/webapp/META-INF/context.xml.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message