Hi Joseph, Try checking out jakarta-tomcat-4.0 and jakarta-tomcat-connectors with tag TOMCAT_4_1_22 or TOMCAT_4_1_18. The failure is due to a recent checkin that broke the build. If you extract the fifteen or so project dependencies into one separate dir, then point your build.properties to that dir, it is pretty good about picking them up. Just step through build.properties and tweak a few version numbers here and there. At any rate, the break of head will not last long.
Keith | -----Original Message----- | From: Joseph Hindin [mailto:[EMAIL PROTECTED] | Sent: Wednesday, March 12, 2003 11:04 AM | To: [EMAIL PROTECTED] | Subject: Compiling from sources | | | For a couple of days I am trying to compile tomcat v4 from sources. | Unfortunately, the experience is not very encouraging. | As a first step, I've tried to compile stable version by downloading | source code tarball. The tarball uses several Jakarta projects. | build.xml files for the subprojects are completely inconsistent, so it | took more than a day to get all subprojects, related technologies, etc. | At the end, the tarball approach failed, as connectors version required | functionality not available in modeler tarball ( | Registry.registerComponent was missing ). | Now I am trying to compile tomcat using CVS. Tomcat | build.properties doesn't fit CVS tree structure; several projects from | commons don't fit, too. | Am I doing something wrong? | --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
