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=6031>. 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=6031 Bootclasspath option for <available> task Summary: Bootclasspath option for <available> task Product: Ant Version: 1.5 alpha (nightly) Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: Core tasks AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] It might be useful, when compiling for different platforms, to be able to specify the bootclasspath for <available>. The current behaviour is to check the classes available to Ant's JVM, which don't necessarily match those in the target device. For example, to determine if actions should be taken for non-CLDC devices (which generally have java.awt.*): <target name="check"> <available property="awt.present" bootclasspath="${cldc.home}/lib/rt.jar" classname="java.awt.Graphics"/> </target> <target name="noncldc" depends="check" if="awt.present"> ... </target> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
