You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/06/25 20:41:24 UTC
DO NOT REPLY [Bug 10225] New: -
ANT Tasks Error Situation
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10225>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10225
ANT Tasks Error Situation
Summary: ANT Tasks Error Situation
Product: Tomcat 4
Version: Nightly Build
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Unknown
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: devlists@logemann.info
for example the org.apache.catalina.ant.StartTask will throw an exception
when you try to start a webapp which is allready running, this results
in a build-error in ANT. But in ANT build files where you emulate
something like hot-deploy in using a stop/startTask combination, there
are situations where you try to start an webapp which is allready running.
There should be an attribute where you can define if you really want
to throw an Exception (aka BuildError) or not.
something like:
<tcstart url="${catalina.url}" username="${catalina.username}"
password="${catalina.password}" path="/maxbahr"/ builderroronfail="false">
The same goes for several other tasks like StopTask for allready stopped
webapps.
Craig mentioned correctly that a distinction between "bad-startup" or
"allready running" would be nice. IMO bad startup (which is mostly some
bad user/pw/path combination) should result in BuildError, but "allready
running" Situation should be left to the user...
I just mentioned StartTask and StopTask, there may be others where the
same pattern could be applied.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>