You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ant.apache.org by Sunny Gulati <sg...@eai.com> on 2000/11/06 20:51:12 UTC

javadoc in ant 1.2 crashes..

Hi, I'm trying to upgrade our build environment to use ant v1.2, but we're
running into a wierd problem.  When it gets to the javadoc command, it
crashes like so:

# ant clean all
...
/usr/local/sgulati/cvs/javaserver/dataserver/build.xml:78: Javadoc failed:
java.io.IOException: javadoc: cannot execute
java.io.IOException: javadoc: cannot execute
        at java.lang.UNIXProcess.forkAndExec(Native Method)
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:134)
        at java.lang.Runtime.execInternal(Native Method)
        at java.lang.Runtime.exec(Runtime.java:268)
        at
org.apache.tools.ant.taskdefs.Execute$CommandLauncher.exec(Execute.java)
        at
org.apache.tools.ant.taskdefs.Execute$CommandLauncherProxy.exec(Execute.java
)
        at
org.apache.tools.ant.taskdefs.Execute$ScriptCommandLauncher.exec(Execute.jav
a)
        at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java)
        at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java)
        at org.apache.tools.ant.Target.execute(Target.java)
        at org.apache.tools.ant.Project.runTarget(Project.java)
        at org.apache.tools.ant.Project.executeTarget(Project.java)
        at org.apache.tools.ant.Project.executeTargets(Project.java)
        at org.apache.tools.ant.Main.runBuild(Main.java)
        at org.apache.tools.ant.Main.main(Main.java)

the javadoc tag looks like this:
        <target name="javadoc" depends="prepare" >
        <javadoc packagenames="com.eai.*"
           sourcepath="${src.home}"
           destdir="${javadoc.home}"
           author="true"
           version="true"
           use="true"
                   package="true"
           windowtitle="eVis API"
           doctitle="&lt;h1&gt;eVis API&lt;/h1&gt;"
           bottom="Copyright &#169; 2000 Engineering Animation, Inc. All
Rights Reserved."
            />
        </target>


However, a coworker's build script, which called ant, seemed to work fine.
My coworker's script was setting up a custom classpath pointing to ant.jar
from version 1.1, and then directly running org.apache.tools.ant.Main.

I can run javadoc just fine from the command line.

I can recreate the javadoc crash consistently on 3 machines; they are all
Redhat Linux 6.x (with slightly different kernels), and we're using Sun's
1.2.2_006 JDK.  Is there a difference in how javadoc is called between ant
v1.1 and v1.2 that would cause this difference?  is there something I can do
to fix it temporarily?  Is it a known bug?  (the bug database has been down,
so I couldn't search it)

Sincerely,
  Sunny Gulati




Re: javadoc in ant 1.2 crashes..

Posted by Jan Castermans <ja...@beta9.be>.
On Monday 06 November 2000 20:51, you wrote:
> Hi, I'm trying to upgrade our build environment to use ant v1.2, but we're
> running into a wierd problem.  When it gets to the javadoc command, it
> crashes like so:
>
> # ant clean all
> ....
> /usr/local/sgulati/cvs/javaserver/dataserver/build.xml:78: Javadoc failed:
> java.io.IOException: javadoc: cannot execute
> java.io.IOException: javadoc: cannot execute
>         at java.lang.UNIXProcess.forkAndExec(Native Method)
>         at java.lang.UNIXProcess.<init>(UNIXProcess.java:134)
>         at java.lang.Runtime.execInternal(Native Method)
>         at java.lang.Runtime.exec(Runtime.java:268)
>         at
> org.apache.tools.ant.taskdefs.Execute$CommandLauncher.exec(Execute.java)
>         at
> org.apache.tools.ant.taskdefs.Execute$CommandLauncherProxy.exec(Execute.jav
>a )
>         at
> org.apache.tools.ant.taskdefs.Execute$ScriptCommandLauncher.exec(Execute.ja
>v a)
>         at org.apache.tools.ant.taskdefs.Execute.execute(Execute.java)
>         at org.apache.tools.ant.taskdefs.Javadoc.execute(Javadoc.java)
>         at org.apache.tools.ant.Target.execute(Target.java)
>         at org.apache.tools.ant.Project.runTarget(Project.java)
>         at org.apache.tools.ant.Project.executeTarget(Project.java)
>         at org.apache.tools.ant.Project.executeTargets(Project.java)
>         at org.apache.tools.ant.Main.runBuild(Main.java)
>         at org.apache.tools.ant.Main.main(Main.java)
>
> the javadoc tag looks like this:
>         <target name="javadoc" depends="prepare" >
>         <javadoc packagenames="com.eai.*"
>            sourcepath="${src.home}"
>            destdir="${javadoc.home}"
>            author="true"
>            version="true"
>            use="true"
>                    package="true"
>            windowtitle="eVis API"
>            doctitle="&lt;h1&gt;eVis API&lt;/h1&gt;"
>            bottom="Copyright &#169; 2000 Engineering Animation, Inc. All
> Rights Reserved."
>             />
>         </target>
>
>
> However, a coworker's build script, which called ant, seemed to work fine.
> My coworker's script was setting up a custom classpath pointing to ant.jar
> from version 1.1, and then directly running org.apache.tools.ant.Main.
>
> I can run javadoc just fine from the command line.
>
> I can recreate the javadoc crash consistently on 3 machines; they are all
> Redhat Linux 6.x (with slightly different kernels), and we're using Sun's
> 1.2.2_006 JDK.  Is there a difference in how javadoc is called between ant
> v1.1 and v1.2 that would cause this difference?  is there something I can
> do to fix it temporarily?  Is it a known bug?  (the bug database has been
> down, so I couldn't search it)
>
> Sincerely,
>   Sunny Gulati
I had a similar problem once, and it was because my destdir was not created. 
Can you check this.

Re: javadoc in ant 1.2 crashes..

Posted by Stefan Bodewig <bo...@bost.de>.
>>>>> "SG" == Sunny Gulati <sg...@eai.com> writes:

 SG> Hi, I'm trying to upgrade our build environment to use ant v1.2,
 SG> but we're running into a wierd problem.  When it gets to the
 SG> javadoc command, it crashes like so:

Seems like Ant cannot find antRun. Did you set the ANT_HOME
environment variable?

 SG> I can recreate the javadoc crash consistently on 3 machines; they
 SG> are all Redhat Linux 6.x (with slightly different kernels), and
 SG> we're using Sun's 1.2.2_006 JDK.

No problems on my box (heavily patched Redhat 6.1 and almost any JDK
for Linux you can think of). 

Stefan