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=25327>. 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=25327 Forked VMs != forking VM, breaking script portability Summary: Forked VMs != forking VM, breaking script portability Product: Ant Version: 1.6Beta Platform: All URL: http://gump.covalent.com/log/ws-axis-test.html OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] If a user (e.g. Gump, or whatever) selects a Java VM (perhaps a certain instance), or sets system properties (e.g. java.awt.headless, or bootclasspath ), forked VMs don't match this. As such, scripts can fail based upon the default environment (which gives the new forked Ant VM). I can see this in three parts: 1) JVM instance (this might just have to be left to the OS path) 2) Classpaths (ought bootclasspath be expressed here, or ought we use endorsded) 3) System properties (default behaviour ought be to clone all). I believe that this is a JVM problem (it ought allow a 'fork'), and I wonder if others have solved it & ant could borrow that. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
