ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glenn McAllister" <>
Subject Re: problems specifing a javadoc doclet
Date Tue, 03 Oct 2000 13:23:39 GMT

What version of Ant are you using?  The 1.1 version made the destdir
attribute of the javadoc task manditory (if memory serves), which breaks
doclets that don't use the -d option.  If you need to use JDox, try getting
one of the nightly builds, where this problem has been fixed.  The destdir
attribute is only required if you aren't using a specific doclet, otherwise
its ignored.

Glenn McAllister
Software Developer. IBM Toronto Lab, (416) 448-3805
"An approximate answer to the right question is better than the
right answer to the wrong question." - John W. Tukey

Please respond to

Subject:  Re: problems specifing a javadoc doclet

On Mon, 2 Oct 2000, Glenn McAllister wrote:

: The problem you are running into is that the destdir attribute translates
: to the -d javadoc command line options.  Unfortunately, -d is _standard
: doclet specific_, not common to javadoc itself.  In all likelyhood
: never used JavaDox) they have a different flag for the output directory.
: If the doclet wasn't being found you would see that error before the -d
: problem.
: Could you show us your command line that works?

sure thing:

/jdk1.2.2/bin/javadoc -docletpath jdox/javadox.jar -doclet
com.componentregistry.javadox.JavaDox -sourcepath . @filelist.txt

from the documentation[1]:
It will generate a file... in the current directory.

as i understand it then, it is the unsupported destdir
attribute of the _doclet_ that's fubar-ing it. you say that
-d is standard doclet specific. the documentation[2] does
say it's optional though:

Options Provided by the Standard Doclet

-d  directory

Specifies the destination directory where javadoc saves the
generated HTML files. (The "d" means
"destination.") _Omitting_ this option causes the files to
be saved to the _current directory_.

if destdir wasn't mandatory, i think i wouldn't be having
this problem.

any workarounds, or should i patch the doclet?

- p

View raw message