problems of using java task to start up a GUI application PLEASE DO NOT REPLY TO THIS MESSAGE. TO FURTHER COMMENT ON THE STATUS OF THIS BUG PLEASE FOLLOW THE LINK BELOW AND USE THE ON-LINE APPLICATION. REPLYING TO THIS MESSAGE DOES NOT UPDATE THE DATABASE, AND SO YOUR COMMENT WILL BE LOST SOMEWHERE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3069 *** shadow/3069 Mon Aug 13 21:21:55 2001 --- shadow/3069.tmp.12673 Wed Aug 15 16:23:35 2001 *************** *** 2,9 **** | problems of using java task to start up a GUI application | +----------------------------------------------------------------------------+ | Bug #: 3069 Product: Ant | ! | Status: NEW Version: 1.3 | ! | Resolution: Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | | Priority: Other Component: Core tasks | +----------------------------------------------------------------------------+ --- 2,9 ---- | problems of using java task to start up a GUI application | +----------------------------------------------------------------------------+ | Bug #: 3069 Product: Ant | ! | Status: RESOLVED Version: 1.3 | ! | Resolution: WONTFIX Platform: PC | | Severity: Normal OS/Version: Windows NT/2K | | Priority: Other Component: Core tasks | +----------------------------------------------------------------------------+ *************** *** 29,32 **** I think the problem is that the applicatioh's main() thread exits, ant gets back control and calls System.exit(). A workaround is using fork="yes". A real solution would be a new option for the java task that immediately ends the ! build, but doesn't call System.exit(). --- 29,38 ---- I think the problem is that the applicatioh's main() thread exits, ant gets back control and calls System.exit(). A workaround is using fork="yes". A real solution would be a new option for the java task that immediately ends the ! build, but doesn't call System.exit(). ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-08-15 16:23 ------- ! Forking is the best bet. GUI programs which exit and rely on the AWT thread to ! keep the JVM alive will not be handled in Ant. Since the class' Main method has ! exited, Ant will believe the <java> task has finished and then go on to ! complete the Ant build, bringing down the GUI with it.
