james.javaman wrote:
Hi Dan,
Sorry if I’m being dense here, but how does the newly compiled code get into
$CATALINA_HOME/webapps/myWebApp?
I don’t see the part in your build.xml where the new changes (newly compiled
changes) make it to the Tomcat directory.
According to your response, ${build} can point anywhere. I mean, lets say
${build} points to: C:\temp\nowhere_of_significance. Wouldn’t this mess up
a reload? The only parameters I see in a reload are a username, password, a
manager url and path of the tomcat web app. Won’t this just reload the same
thing (without our new change.) Is there something happening "under the
hood" I just can't see here where the compiled code magically gets put into
the Tomcat directory?
Thanks for your patience.
Yes ${build} can point to anywhere. I have ${build} in my build.xml file
set to $CATALINA_HOME/webapps/myWebApp/WEB-INF/classes, so the newly
compiled code simply goes to that directory.
Therefore, you specify ${build} to be where you want your compiled code
to go in your webapp (most likely in the path I just showed). There is
nothing else to it; the code gets compiled to your webapp directory,
then you reload the webapp. Reload will not occur until your code is
done compiling, as there is a depends parameter for the reload target.
The reason you can call
ant reload
without calling
ant javac
is because reload depends on javac in the example I provided; it will
not happen unless javac happens. Therefore, calling
ant reload
will also cause the javac command to execute.
Dan
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
