DO NOT REPLY [Bug 14925] New: - Skipping first sourcefile when a custom param with an empty value is added in a javadoc task

[bu...@apache.org]

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=14925>.
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=14925

Skipping first sourcefile when a custom param with an empty value is added in a javadoc task

           Summary: Skipping first sourcefile when a custom param with an
                    empty value is added in a javadoc task
           Product: Ant
           Version: 1.5.1
          Platform: All
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core tasks
        AssignedTo: ant-dev@jakarta.apache.org
        ReportedBy: jeroen.vanagt@philips.com


When a param is added using createParam() method to a JavaDoc task and the 
param value is an empty string it causes the first sourcefile to skip because 
the sourcefile is seen as the first param value (in the javadoc commandline).

param = doclet.createParam();
param.setName("-customparams");
param.setValue("");

The reason is clear if you look into the source (every javadoc API method is 
converted in a single commandline), but it is unclear when reading the 
documentation.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>