You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by bu...@apache.org on 2003/08/14 17:39:56 UTC

DO NOT REPLY [Bug 22244] - Javadoc Task.. Don't use the JAVADOC exceutable from running VM

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22244>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22244

Javadoc Task.. Don't use the JAVADOC exceutable from running VM

bodewig@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Normal                      |Enhancement



------- Additional Comments From bodewig@apache.org  2003-08-14 15:39 -------
Currently it is hardcoded to use the javadoc executable of the VM Ant is
running in.

The easy fix would be to simply add an executable attribute to the task and
you'd supply the full path of the executable you want to run.

Unfortunately things are not that easy as this tasks has tons of conditional
code that adds or not adds attributes based on the javadoc version it is going
to run - and all these conditionals use the current VM to determine which
arguments to support.

In your case, you wouldn't be able to use -1.1 for example as Ant would say
"Javadoc 1.4 doesn't support the -1.1 switch anymore" - even though you
intend to use a 1.3 version of javadoc.

I don't say it's not doable, but a bit more tricky than it seems.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org