Return-Path: Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 76122 invoked from network); 28 Dec 2000 19:10:26 -0000 Received: from msp-65-25-234-27.mn.rr.com (HELO localhost.localdomain) (65.25.234.27) by h29.sny.collab.net with SMTP; 28 Dec 2000 19:10:26 -0000 Received: from fatman (IDENT:nobody@localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.9.3) with SMTP id NAA25203 for ; Thu, 28 Dec 2000 13:06:52 -0600 Message-ID: <3753023.978030412000.JavaMail.nobody@fatman> Date: Thu, 28 Dec 2000 13:06:51 -0600 (CST) From: BugRat Mail System Reply-To: BugRat Mail System To: ant-bugs@cortexity.com Subject: BugRat Report #672 has been filed. Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="4067003.978030411967.JavaMail.nobody@fatman" X-Mailer: org.gjt.mail.EnhancedMimeMsg, Organization: The Giant Java Tree, X-Spam-Rating: h29.sny.collab.net 1.6.2 0/1000/N --4067003.978030411967.JavaMail.nobody@fatman Content-Type: text/plain Content-Transfer-Encoding: 7bit Bug report #672 has just been filed. You can view the report at the following URL: REPORT #672 Details. Project: Ant Category: Bug Report SubCategory: New Bug Report Class: swbug State: received Priority: low Severity: serious Confidence: public Environment: Release: 1.2 JVM Release: jdk1.3 Operating System: Linux OS Release: Red Hat Linux 6.1 Platform: x86 Synopsis: $PATH handling buglet Description: When building a target that needs to execute javadoc (for instance, one including the javadoc element), and there is a directory named 'javadoc' in a directory in your $PATH before the 'javadoc' executable, the following error occurs: Buildfile: ./build.xml init: ##### ${company} ${product} ${version} #### javadoc: [javadoc] Generating Javadoc [javadoc] Javadoc execution BUILD FAILED /home/broz/foo/./build.xml:40: Javadoc failed: java.io.IOException: javadoc: canno\ t execute java.io.IOException: javadoc: cannot execute at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:137) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:551) at java.lang.reflect.Method.invoke(Native Method) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execut\ e.java:390) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:247) at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java:728) at org.apache.tools.ant.Target.execute(Target.java:142) at org.apache.tools.ant.Project.runTarget(Project.java:818) at org.apache.tools.ant.Project.executeTarget(Project.java:532) at org.apache.tools.ant.Project.executeTargets(Project.java:506) at org.apache.tools.ant.Main.runBuild(Main.java:420) at org.apache.tools.ant.Main.main(Main.java:149) Total time: 1 second I argue that this is a bug, since the shells which I have tried (bash, csh) do not exhibit this behavior (preferring the directory to a file later in the $PATH). It might be worth checking UNIX standards. Email me if you'd like the build files I used to test this; I'll probably want to clean them up a bit. This quite probably affects non-javadoc targets. --4067003.978030411967.JavaMail.nobody@fatman Content-Type: text/html; name=Report-672.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=Report-672.html Content-Description: DataSource attachment 'Report-672.html' BugRat Report # 672

BugRat Report # 672

Project: Ant Release: 1.2
Category: Bug Report SubCategory: New Bug Report
Class: swbug State: received
Priority: low Severity: serious
Confidence: public

Submitter: Vince Broz ( broz+ant@andrew.cmu.edu )
Date Submitted: Dec 28 2000, 01:06:51 CST
Responsible: Z_Ant Alias ( ant-bugs@cortexity.com )

Synopsis:
$PATH handling buglet
Environment: (jvm, os, osrel, platform)
jdk1.3, Linux, Red Hat Linux 6.1, x86

Additional Environment Description:
This is probably UNIX-specific, and may be a bug in an underlying library. I have a feeling that this is actually a bug in the 1.3 JDK, but didn't track it down far enough to find out. In any case, you might add a note in the documentation to save people the trouble of isolating the problem.

Report Description:
When building a target that needs to execute javadoc (for instance, one including the javadoc element), and there is a directory named 'javadoc' in a directory in your $PATH before the 'javadoc' executable, the following error occurs: Buildfile: ./build.xml init: ##### ${company} ${product} ${version} #### javadoc: [javadoc] Generating Javadoc [javadoc] Javadoc execution BUILD FAILED /home/broz/foo/./build.xml:40: Javadoc failed: java.io.IOException: javadoc: canno\ t execute java.io.IOException: javadoc: cannot execute at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:137) at java.lang.Runtime.execInternal(Native Method) at java.lang.Runtime.exec(Runtime.java:551) at java.lang.reflect.Method.invoke(Native Method) at org.apache.tools.ant.taskdefs.Execute$Java13CommandLauncher.exec(Execut\ e.java:390) at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java:247) at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java:728) at org.apache.tools.ant.Target.execute(Target.java:142) at org.apache.tools.ant.Project.runTarget(Project.java:818) at org.apache.tools.ant.Project.executeTarget(Project.java:532) at org.apache.tools.ant.Project.executeTargets(Project.java:506) at org..apache.tools.ant.Main.runBuild(Main.java:420) at org.apache.tools.ant.Main.main(Main.java:149) Total time: 1 second I argue that this is a bug, since the shells which I have tried (bash, csh) do not exhibit this behavior (preferring the directory to a file later in the $PATH). It might be worth checking UNIX standards. Email me if you'd like the build files I used to test this; I'll probably want to clean them up a bit. This quite probably affects non-javadoc targets.

How To Reproduce:
null

Workaround:
null

View this report online...
--4067003.978030411967.JavaMail.nobody@fatman--