First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 49128
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Java team <java@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Niek van der Maas <webmaster@refstart.nl>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
build.xml Sample build.xml file text/plain Andrew Roberts 2004-05-01 07:21 0000 109 bytes Details
build.xml Sample build.xml file text/xml Niek van der Maas 2004-06-02 23:12 0000 195 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 49128 depends on: Show dependency tree
Bug 49128 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-04-26 23:22 0000 
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:

------- Comment #1 From Andrew Roberts 2004-05-01 07:21:05 0000 ------- 
Created an attachment (id=30448) [details]
Sample build.xml file

Can't verify this bug. Sample build.xml with <exec> works fine.
Suggest invalid.

------- Comment #2 From Karl Trygve Kalleberg (RETIRED) 2004-06-02 13:28:18 0000 ------- 
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?

------- Comment #3 From Niek van der Maas 2004-06-02 23:12:22 0000 ------- 
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.

------- Comment #4 From Niek van der Maas 2004-06-02 23:12:53 0000 ------- 
Created an attachment (id=32565) [details]
Sample build.xml file

------- Comment #5 From Todd de Gruyl 2004-06-12 09:18:48 0000 ------- 
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

------- Comment #6 From Karl Trygve Kalleberg (RETIRED) 2004-06-12 10:56:22 0000 ------- 
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.
First Last Prev Next    No search results available      Search page      Enter new bug