Ok, I found the problem with the "update" attribute (Ant wasn't configured correctly and was still referencing an older catalina-ant.jar).
Should the "reload" target depend on "compile"? Rob Abernethy Dynamic Edge, Inc. -----Original Message----- From: Robert D. Abernethy IV [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2003 10:53 AM To: 'Tomcat Users List' Subject: Tomcat 5 Deployer Has anyone had success deploying a web application using the new Deployer package? I have tried to use it, but I am receiving this error: deploy: [deploy] BUILD FAILED: file:C:/eclipse/workspace/Alpaca/build.xml:104: The <deploy> task doesn't support the "update" attribute. I also found it difficult to find any information on how to actually use the Deployer. The web site mentions it functionality, but does not provide concrete instructions or examples. For example, the Deployer package comes with a lib directory that contains many JAR files already provided by Tomcat. Should the classpath be changed to look at the common/shared lib directories of Tomcat, or should those JAR files be included with the webapp? Along those same lines, the build.xml file that ships with the Deployer package doesn't reference Tomcat when compiling the source files - it only looks for JAR files within the webapp itself. Is it a better practice to have several copies of a JAR file stored in every individual webapp the requires them, or to have one JAR file in the common/shared lib directory that is shared among all webapps? Any additional information on the Deployer would be appreciated. Thanks. Rob Abernethy Dynamic Edge, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
