You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2001/10/04 01:56:25 UTC
DO NOT REPLY [Bug 3956] New: -
would a troubleshooting script be possible to health check installations?
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=3956>.
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=3956
would a troubleshooting script be possible to health check installations?
Summary: would a troubleshooting script be possible to health
check installations?
Product: Ant
Version: 1.5 alpha (nightly)
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Wrapper scripts
AssignedTo: ant-dev@jakarta.apache.org
ReportedBy: steve_l@iseran.com
I was wondering, after the fun of dealing with a slighly messed up ant config
on a server recently, whether it would be possible to code up a troubleshoot-
ant-installation.{sh,bat,perl,py} routine to sanity check an an ant
installation.
something on the lines of
-check JAVA_HOME
-verify java lives under JAVA_HOME
-run java to probe for java being on the path
-check ANT_HOME, print it out
-check for ANT_HOME\bin\ant.whatever
-check for ANT_HOME\bin\lcp.bat
and any other configuration show stoppers that stop ant from starting properly.
Of course, if we can move away from a startup script at all, almost none of the
tests are needed 'cept maybe java probing.