Community
Participate
Working Groups
Build ID: 20090621-0832 Steps To Reproduce: 1. Set the value of Preferences > Ant > Runtime > Classpath > Ant Home... to a valid Ant installation. 2. Create and execute an Ant build under the External Tools menu. 3. Change the Ant Home setting to a non-existant directory 4. Try to repeat the Ant build 5. The console shows a non-terminating wait cursor (until the build is manually stopped). 6. The error log shows: eclipse.buildId=I20090611-1540 java.version=1.6.0_13 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Error Fri Jul 24 11:53:01 BST 2009 Error logged from Ant UI: java.net.SocketTimeoutException: Accept timed out at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:384) at java.net.ServerSocket.implAccept(ServerSocket.java:453) at java.net.ServerSocket.accept(ServerSocket.java:421) at org.eclipse.ant.internal.ui.launchConfigurations.RemoteAntBuildListener$ServerConnection.run(RemoteAntBuildListener.java:95) More information: I had Ant builds working fine from Eclipse, then upgraded my Ant installtion to a new version in a new ANT_HOME directory. This invalidated the Ant Home setting in Eclipse. I would have expected a much clearer indication that Eclipse could not find a runnable Ant at the directory it was given. Instead, I just got the socket timeout exception listed above in the error log, and no user feedback at all on the Ant console. Once I corrected the Ant Home setting, my ant builds worked fine.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
