| # The Apache Tomcat 5.5 Servlet/JSP Container |

Links Docs Home FAQ User Guide 1) Introduction 2) Setup 3) First webapp 4) Deployer 5) Manager 6) Realms and AAA 7) Security Manager 8) JNDI Resources 9) JDBC DataSources 10) Classloading 11) JSPs 12) SSL 13) SSI 14) CGI 15) Proxy Support 16) MBean Descriptor 17) Default Servlet 18) Clustering 19) Load Balancer 20) Connectors 21) Monitoring and Management 22) Logging 23) APR 24) Virtual Hosting Reference Release Notes Apache Tomcat Configuration JK 1.2 Documentation Servlet API Javadocs JSP API Javadocs Apache Tomcat Development Building Changelog Status Developers Functional Specs. Apache Tomcat Javadocs Apache Jasper Javadocs Architecture | # The Apache Tomcat 5.5 Servlet/JSP Container ## Building Tomcat
Table of Contents
README Introduction Download and install a Java Development Kit 1.4.x or later Install Apache Ant 1.6.2 or later Building Tomcat Updating and rebuilding Tomcat sources Building with Eclipse Building with other IDEs
README
This document duplicates some of the information from the BUILDING.txt file included in every Tomcat distribution. You may want to consult both.
Introduction
Building Tomcat from SVN is very easy, and is the first step to contributing to Tomcat. The following is a step by step TODO list.
Download and install a Java Development Kit 1.4.x or later
The default distribution of Tomcat 5.5.x requires a 5.0 or later JDK. Tomcat can be built using a 1.4.x JDK but you will need to copy the contents of the compat directory (created by the build process) to your build directory before Tomcat will start. The Sun JDK can be downloaded here. IMPORTANT: Set an environment variable JAVA_HOME to the pathname of the directory into which you installed the JDK release.
Install Apache Ant 1.6.2 or later
Download a binary distribution of Ant 1.6.2 or later from here. Unpack the binary distribution into a convenient location so that the Ant release resides in its own directory (conventionally named "apache-ant-1.6.x"). For the purposes of the remainder of this document, the symbolic name "${ant.home}" is used to refer to the full pathname of the release directory. Create an ANT_HOME environment variable to point the directory ${ant.home}, and modify the PATH environment variable to include directory "${ant.home}/bin" in its list. This makes the "ant" command line script available, which will be used to actually perform the build.
Building Tomcat
Download the main build.xml script from here. Create a new directory, and copy the newly download build.xml to it. This directory will be referred to as the ${tomcat.source} directory in the rest of this document. Go to that directory, and do: `cd ${tomcat.source} ant` NOTE: Users accessing the Internet through a proxy must use a properties file to indicate to Ant the proxy configuration. Read below. WARNING: Running this command will checkout the Tomcat 5 sources from SVN, as well as download binaries to the `/usr/share/java` directory. Make sure this is appropriate to do so on your computer. On Windows, this usually corresponds to the `C:\usr\share\java` directory, unless Cygwin is used. Read below to customize the directory used to download the binaries. The build can be controlled by creating a ${tomcat.source}/build.properties file, and adding the following content to it: `# ----- Proxy setup ----- # Uncomment if using a proxy server. #proxy.host=proxy.domain #proxy.port=8080 #proxy.use=on # ----- Default Base Path for Dependent Packages ----- # Replace this path with the directory path where # dependencies binaries should be downloaded. base.path=/usr/share/java`
Updating and rebuilding Tomcat sources
It is recommended to regularly update the downloaded Tomcat 5 sources. To do this, execute the following commands: `cd ${tomcat.source} ant checkout` For a quick rebuild of only modified code you can use: `cd ${tomcat.source} ant build`
Building with Eclipse
> Important: This is not a supported means of building Tomcat; this information is provided without warranty :-). The only supported means of building Tomcat is with the "ant build" described above. However, some developers like to work on Java code with a Java IDE, and the following steps have been used by some developers. Note that you must complete all the above steps to fetch the repositories and build some JAR files the first time. After you have completed the above steps, you can set up a series of Eclipse 4 projects. Note that this will not let you build everything under Eclipse; the build process requires use of Ant for the many stages that aren't simple Java compilations. However, it will allow you to view and edit the Java code, get warnings, reformat code, perform refactorings, run Tomcat under the IDE, and so on. You will want to set up your Eclipse project for building Tomcat such that ${tomcatSource} is the Workspace folder. Use Windows->Preferences and then Java->Build Path->Classpath Variables to add two new Classpath variables:
> TOMCAT_LIBS_BASE | the base path where the binary dependencies have been downloaded
> ANT_HOME | the base path of Ant 1.6.2 or later
Use File->New Project to create a new Java project for each of the binaries repository (e.g., /usr/share/java), container, connectors, jasper, servletapi. If you didn't already set up the Eclipse project such that ${tomcat.source} is the Workspace folder, do so now: tell Eclipse the external location using "Import/Export...", General->Existing Project into Workspace. Eclipse .project and .classpath files are provided in each of these directories so Eclipse should find all source trees and jars, and hopefully compile without problems. Note that these files assume you are using Eclipse with a 5.0 or later JDK; also, the connectors module must be built with a compiler compliance level of 5.0. To run Tomcat without a special IDE plug-in, you can simply use Run->Run... enter "org.apache.catalina.startup.Catalina" as the main class, "start" as program arguments, and "-Dcatalina.home=..." (with the name of your build directory) as VM arguments. Note also that due to the way the Tomcat source is assembled from several SVN projects, you may not be able to use the Eclipse SVN client to update (nor to commit, if you are a committer). Use the external SVN client of your choice, then use the Eclipse PackageExplorer or Navigator "Refresh" context menu item to tell Eclipse that you've updated the files.
Building with other IDEs
The same caveats apply as for Eclipse, above. The same general idea should work in most IDEs; it has been reported to work in Idea, for example.
Copyright © 1999-2011, Apache Software Foundation