Community
Participate
Working Groups
Build Identifier: 20100617-1415 When I try to run Ant on my build.xml, the Console window shows that the Ant build terminated and the window is blank. This happens regardless of what target I choose in the launch config. Reproducible: Always Steps to Reproduce: 1. Right-click build.xml -> Run As -> Ant Build 2. Console window heading displays: <terminated> build.xml [Ant Build] /usr/lib/jvm/java-6-openjdk/bin/java 3. Console window has no output
Can you attach a sample script?
Created attachment 172640 [details] Simple Ant build script I experience the problem with even the simplest Ant build script
This problem does not affect win32 platform
I was able to workaround the issue by changing ANT_HOME to /usr/share/ant
This works for me on Win XP and UBuntu. What linux are you using? If you restore default settings for Ant Runtime preferences do things work?
(In reply to comment #5) > This works for me on Win XP and UBuntu. What linux are you using? If you > restore default settings for Ant Runtime preferences do things work? I'm running Debian squeeze amd64. The only way I could get it to work was by pointing Ant Home to /usr/share/ant which is where Debian keeps all the files used for Ant.
(In reply to comment #6) > > The only way I could get it to work was by pointing Ant Home to /usr/share/ant > which is where Debian keeps all the files used for Ant. I managed to reproduce the same behavior (on Ubuntu 10.04) but not sure it is the same cause. In my case I was mucking around and had removed the antlibsupport.jar file, after that no Ant task would ever output anything, even using the attached example nothing would appear in the console. I would get an exception in the error log about the missing jar though. Jason, do you recall seeing any exceptions in your error log about this jar being missing?
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.
