libreccm-legacy/ccm-core/application.xml

46 lines
1.8 KiB
XML
Executable File

<?xml version="1.0"?>
<ccm:application xmlns:ccm="http://ccm.redhat.com/ccm-project"
name="ccm-core"
prettyName="Core"
version="6.7.1"
release="1"
shared="true"
webapp="ROOT"
buildHooks="build-hooks.xml">
<ccm:dependencies>
<ccm:buildRequires name="httpunit" version="1.5.4" relation="ge"/>
<ccm:buildRequires name="junit" version="3.8.1" relation="ge"/>
<ccm:buildRequires name="junitperf" version="1.8" relation="ge"/>
<ccm:buildRequires name="servlet-api" version="2.5" relation="ge"/>
<ccm:buildRequires name="jsp-api" version="2.1" relation="ge"/>
<ccm:buildRequires name="portlet" version="2.0" relation="ge"/>
<!-- Oracle JDBC driver may not be part of CCM distribution by licence.
Has to be handled separately. -->
<!-- <ccm:buildRequires name="ojdbc14"/> -->
<ccm:runRequires name="servlet-api"/>
<ccm:runRequires name="jsp-api"/>
</ccm:dependencies>
<!-- DEPRECATED
Up to version APLAWS+ 1.0.5 / CCM 6.5 the system used an application
specific URL resource: protocol extension which required a system jar
file to be distributed to a special directory in Tomcat and a special
Tomcat configuration (ext.lib.dir).
Now replaced by standard compliant code. Mechanism preserved here as an
template just in case needed for another purpose.
<ccm:systemPackages>
<ccm:package path="com/arsdigita/util/protocol/"/>
</ccm:systemPackages>
-->
<ccm:contacts>
<ccm:contact uri="http://www.redhat.com/software/rhea" type="website"/>
<ccm:contact uri="mailto:rhea@redhat.com" type="support"/>
</ccm:contacts>
<ccm:description>
The Red Hat Web Application Framework is a platform for writing
database-backed web applications in Java.
</ccm:description>
</ccm:application>