I'm using ant-1.6.1-r1. When i try to add a <exec> tag to my build.xml I get this error: BUILD FAILED /home/.../build.xml:18: Execute failed: java.io.IOException: java.io.IOException: /usr/share/ant/bin/antRun: not found The fix: $ mkdir /usr/share/ant/bin $ ln -sf /usr/bin/antRun /usr/share/ant/bin/antRun Reproducible: Always Steps to Reproduce:
Created attachment 30448 [details] Sample build.xml file Can't verify this bug. Sample build.xml with <exec> works fine. Suggest invalid.
I cannot seem to reproduce this bug. If it still persists, can you trim down your build.xml file and create a dummy project that can reproduce it for me and attach it to this bug, then reopen it?
First, sorry for the somewhat late reply and incomplete info in my first comment. Second, I just discovered the bug only seems to occur when the vmlauncher attribute is set to false. I'll upload a test case. Hope this helps, Niek.
Created attachment 32565 [details] Sample build.xml file
I also see this behavior. This patch fixed it for me (using ant-1.6.1.ebuild since that's the latest one marked with ~ppc, but I think a similar approach should work for all of the ant ebuilds.) *** /usr/portage/dev-java/ant/ant-1.6.1.ebuild Sun May 16 14:49:02 2004 --- ant-1.6.1.ebuild Sat Jun 12 11:50:12 2004 *************** *** 70,75 **** --- 70,80 ---- dobin ${S}/src/script/${each} done + dodir /usr/share/ant/bin + for each in antRun runant.pl runant.py complete-ant-cmd.pl; do + dosym /usr/bin/${each} /usr/share/ant/bin/${each} + done + insinto /etc/env.d doins ${FILESDIR}/20ant
Fixed. I should've bumped the revision on this, but that's a bit tricky because of the different platform keywords for 1.6.1 and 1.6.1-r1. We should collate the two revisions in -r2 soon.
