Return-Path: 
 <users-return-156266-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org>
Delivered-To: apmail-tomcat-users-archive@www.apache.org
Received: (qmail 49209 invoked from network); 4 Jan 2007 20:35:47 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Jan 2007 20:35:47 -0000
Received: (qmail 91105 invoked by uid 500); 4 Jan 2007 20:35:40 -0000
Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org
Received: (qmail 91079 invoked by uid 500); 4 Jan 2007 20:35:40 -0000
Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@tomcat.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@tomcat.apache.org>
List-Post: <mailto:users@tomcat.apache.org>
List-Id: <users.tomcat.apache.org>
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Delivered-To: mailing list users@tomcat.apache.org
Received: (qmail 91068 invoked by uid 99); 4 Jan 2007 20:35:40 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2007 12:35:40 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of carlosjosepita@gmail.com
 designates 66.249.82.229 as permitted sender)
Received: from [66.249.82.229] (HELO wx-out-0506.google.com) (66.249.82.229)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jan 2007 12:35:31 -0800
Received: by wx-out-0506.google.com with SMTP id i26so6589513wxd
        for <users@tomcat.apache.org>; Thu, 04 Jan 2007 12:35:10 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=Huf6t1uIQncU9YDLOdjfuah45L6G5+yO2S/JEN5fIY3gb5lLPJlBpgphuUmJJHk59FwkCpxXMZdeuOnRzakMvWAymbICggWbc1ds/QN8kVPq+iUIsm94n83T1ibOzQmGPX6Jr84sS9vpF111lqOQvfgIzVnUZVzsfazSCbJrV3M=
Received: by 10.70.74.1 with SMTP id w1mr26294682wxa.1167942910456;
        Thu, 04 Jan 2007 12:35:10 -0800 (PST)
Received: by 10.65.11.2 with HTTP; Thu, 4 Jan 2007 12:35:10 -0800 (PST)
Message-ID: <7798eaa0701041235w2e16c55bv2304573427e2cea4@mail.gmail.com>
Date: Thu, 4 Jan 2007 17:35:10 -0300
From: "Carlos Pita" <carlosjosepita@gmail.com>
To: users@tomcat.apache.org
Subject: Deploy from ant
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Virus-Checked: Checked by ClamAV on apache.org

Hi all,

how do I deploy a webapp from the ant deploy task avoiding it to copy
the entire application under tomcat/webapps? The point is to simply
update my build directory with modified jsps to make tomcat aware of
the changes. If this build directory, which of course is not under
webapps, is first copied under webapps by the ant deploy task, then
nothing is updated there each time I build the app, and instead I have
to explicitly redeploy it. One solution that comes to my mind is to
deploy an xml context descriptor instead of a exploded war directory.
But anyway, from the documentation here:

http://tomcat.apache.org/tomcat-6.0-doc/appdev/source.html
http://tomcat.apache.org/tomcat-6.0-doc/appdev/processes.html

I would infer that deploying my application by means of a target like

  <target name="tomcat-deploy" depends="init,build,init-ant"
description="Deploy application to servlet container">
    <tomcat-deploy url="${tomcat.manager.url}"
username="${tomcat.manager.username}"
                   password="${tomcat.manager.password}"
path="${tomcat.context.path}"
                   war="file://${project.build.path}" />
 </target>

will in principle install the application into tomcat without copying
it into webapps, which in practice it doesn't.  The following excerpts
from the above links seem to support my supposition:

"""
For interactive development and testing of your web application using
Tomcat 5, the following additional targets are defined:

    * install - Tell the currently running Tomcat 5 to make the
application you are developing immediately available for execution and
testing. This action does not require Tomcat 5 to be restarted, but it
is also not remembered after Tomcat is restarted the next time.
"""

(notice that the install target uses the deploy task, despite of its name)

"""
# Modify and rebuild as needed. As you discover that changes are
required, make those changes in the original source  files, not in the
output build directory, and re-issue the ant compile command. This
ensures that your changes will be available to be saved (via cvs
commit) later on -- the output build directory is deleted and
recreated as necessary.

# Reload the application. Tomcat will recognize changes in JSP pages
automatically, but it will continue to use the old versions of any
servlet or JavaBean classes until the application is reloaded. You can
trigger this by executing the ant reload command.
"""

Can you help me? I find this very confusing.

Thank you in advance.

Regards,
Carlos

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org