This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
See Ant bug 6456 http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6456 It has been fixed, so an integration with a later Ant should solve the problem. XP generates an error dialog "C:\WINDOWS\system32\ntvdm.exe Error while setting up environment for the application. Choose 'Close' to terminate the application. <Close> <Ignore>"
Thank you for pointing out this problem. I absolutely agree that we should integrate the newer version of Ant. However, I don't see any reason why this issue should be P1 DEFECT for NetBeans module. So I'm changed it to P1 TASK. Let me know if you (or anybody else) disagree. I would also like to ask a question about this Ant's bug. Do you know in which version of Ant the bugfix will be integrated? Is it part of the 1.5 release?
The bug is fixed in Ant 1.5 according to the WHATSNEW document in sources. *** This issue has been marked as a duplicate of 23076 ***
David, I think it's a P1 issue becuase on Win XP, JDK 1.4 ( which I and my company has) The Ant module does not work at all. I also belive its more a defect than a task because the Netbeans Ant module could be immediatly modifyed to allow one of the published workarounds that will permit it to work, and allow other Ant functionality through command line switches. Of course I can also see your point. If you think that the XP + 1.4 jdk combination is not common enough to rate a p1 defect, than I understand.
The workaround suggested on the Apache site, to set -Dos.name="Windows XP" (I guess they mean -Dos.name="Windows NT"), cannot be used exactly as is with NetBeans because NB does not spawn a new process for Ant. NB could set the system property in its VM before running Ant and then change it back; could in principle break some code running at the same time as Ant, but not likely. Anyway, such a patch would mean a new release of the Ant integration module, either as part of NB 3.4 or before, meaning a fair amount of work to test and publish (though the fix by itself would surely be tiny). If Ant 1.5 will not be integrated reasonably soon, this would make sense, otherwise I would recommend we wait for Ant 1.5 and use its official fix. Note that no one is saying XP + 1.4 is a low-priority combination; rather that the bug is a bug in Ant which has not yet even made it into an official Ant release. NetBeans should track Ant releases IMHO, not try to jump ahead of them.
Charlweed, I'm a bit confused. You wrote: "The Ant module does not work at all". I've succesfully tested Ant module on Win XP without any major problems. Please could you describe your problem more. If I understand ant (application) bug reports well, the problem is "only" when using <property environment="env"/>. I understand that it can be crucial part of your project, but has nothing to do with Ant module itself. I happens even when you execute that script outside of NetBeans.
My mistake, I did not test without the <property environment="env"/> I incorrectly assumed that this would be a partof any on trivial build script. Charles