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=24694>. 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=24694 JAVA_HOME should be exported Summary: JAVA_HOME should be exported Product: Ant Version: 1.5.4 Platform: Macintosh OS/Version: MacOS X Status: NEW Severity: Enhancement Priority: Other Component: Wrapper scripts AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] The new ant wrapper shell script automatically determines what the JAVA_HOME variable should be set to, but it should also export the variable so the entire ant build process can have access to it. For instance, I use ant to build my java files, create my native JNI headers using javah, and then to compile the native code by exec-ing a shell script which I populate from the ant buildl.xml. Within this script I need to know where JAVA_HOME is so I can include the jni.h file in my C compilation path. Previous to your new wrapper script, I had my own, which exported JAVA_HOME and all worked wonderfully. I have made the following one line change to your script and would suggest something similar: case "`uname`" in CYGWIN*) cygwin=true ;; Darwin*) darwin=true if [ -z "$JAVA_HOME" ] ; then JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Home export JAVA_HOME fi ;; esac Thanks for listening, and keep up the excellent work! Ant is great! Cheers, Levi --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
