Improved Javadoc Task

[Stefano Mazzocchi <st...@apache.org>]

People,

since many reported problems with both the ant security manager and the
javadoc task, I patched ant and now it shines. Here's what I did:

1) removed the ant security manager. Now ant compiles with no problems
on both java 1.1 1.2 and 1.3

2) changed javadoc2.java to javadoc.java, added the <javadoc> task but
left the <javadoc2> task for temporary back compatibility. NOTE: you
should change all your <javadoc2> tasks with <javadoc> ASAP!!! since
<javadoc2> is deprecated.

(question: should we have a standard run-time way to indicate task
deprecation so that one can go ahead and remove the warnings?)

3) now javadoc works with both java1.1 and java1.2 javadoc (even if I
still have some problems with finding files on javadoc 1.1, but this is
a small issue: help is appreciated since I don't care about 1.1 that
much)

4) patched code so that now works on java 1.1 with no problems and fixed
Sam code that was not working.

5) added double-buffering to the java parsing stage that improved
package evaluation speed by 1000% percent!!!

6) made javadoc extend exec, so that it spanws another JVM. Note: this
is required since javadoc calls system.exit() and breaks ant execution
if executed in the same JVM. performance penalties turn out to be very
small.

Update your ant :)

-- 
Stefano Mazzocchi      One must still have chaos in oneself to be
                          able to give birth to a dancing star.
<st...@apache.org>                             Friedrich Nietzsche
--------------------------------------------------------------------
 Come to the first official Apache Software Foundation Conference!  
------------------------- http://ApacheCon.Com ---------------------

Re: Improved Javadoc Task

[James Duncan Davidson <ja...@eng.sun.com>]

Stefano Mazzocchi wrote:
> (question: should we have a standard run-time way to indicate task
> deprecation so that one can go ahead and remove the warnings?)

I don't think that we want tasks to get that tightly bound. Since we
still (we do, don't we?) have the <taskdef..> mechanism, we don't want
to necessarily prejudice the namespace.

> 6) made javadoc extend exec, so that it spanws another JVM. Note: this
> is required since javadoc calls system.exit() and breaks ant execution
> if executed in the same JVM. performance penalties turn out to be very
> small.

Cool enough. Javadoc takes enough time anyway that the vm startup isn't
that big a deal.


-- 
James Davidson                                     duncan@eng.sun.com 
Java + XML / Portable Code + Portable Data                 !try; do()