I noticed that you recently updated the build.xml to include a cycle for
Jo!.  Having recently attempted to build Sevak using Catalina I thought you
should know that your build.xml is out of date.

  -  <!-- Tomcat Jars -->
  -  <!-- <property name="catalina-version" value="4.0.7"/> -->
  -  <property name="catalina-version" value="4.1.7"/>
  -  <property name="catalina-dir-suffix" value="-beta"/>

  -    <get
src="http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v${catalina
-version}${catalina-dir-suffix}/bin/jakarta-tomcat-${catalina-version}.zip"
  -    dest="catalina-download/catalina-${catalina-version}.zip"
  -    verbose="true"
  -    usetimestamp="true"/>

This version is no longer present causing the Ant <get ../> to fail.  My
solution was to use

  <property name="catalina.jars.loc"
value="http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v${catali
na-version}${catalina-dir-suffix}/bin/jakarta-tomcat-${catalina-version}-LE-
jdk14.zip"/>

    <get src="${catalina.jars.loc}"
    dest="catalina-download/catalina-${catalina-version}.zip"
    verbose="true"
    usetimestamp="true"/>

this way as new Catalina updates are made available, users can override the
${catalina.jars.loc} property in a .ant.properties without needing to modify
the actual build.xml  There are several other <get .../> tasks that could
also benefit from this refactoring.

I also had a question about the CatalinaSevakImpl.  Does this implementation
use the standard server.xml during initialize( )?  As it does not appear to
do so, could this be considered as a possibility?  Doing so would allow
standard administration of Tomcat, I believe.

Daniel Krieg


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to