Since the only place this seems to cause trouble is with projects that
do not use packages, I'd suggest a simple modification to the javadoc
task as follows:
1. If the sourcefiles attribute DOES NOT contain a '*', then process it
as is done today (i.e., assume it's a list of files).
2. If it DOES contain a '*', then create a fileset using the sourcepath
and the pattern specified in the sourcefiles and use the resulting file
list as input to the javadoc command.
I think this simple change would address most of the javadoc problems
I've seen raised in the last couple of weeks.
Comments?
Bill.J.Fellows@mail.sprint.com wrote:
>
> I'd always thought that was a limitation for javadoc (either the task
> or the binary). It'd be far cooler to be able to say <javadoc
> sourcepath="src" sourcefiles="**/*.java" /> and have it find all java
> files below. Worse case scenario would be to pass a comma-delimited
> string back with the results from the search. I could be willing to
> look into riggin' something like that up if it'd be useful. I'd need
> to investigate how the patternset/fileset stuff actually works but I
> don't think it'd terribly difficult. Any thoughts, hints, suggestions?
>
> /bill
>
> -----Original Message-----
> From: streepy [mailto:streepy@healthlanguage.com]
> Sent: Thursday, June 21, 2001 12:09 PM
> To: ant-user
> Cc: streepy
> Subject: Re: javadoc help
>
> After some investigation, it seems that the javadoc task does not deal
> well with files that are not in a package. You will have to list the
> source files specifically using the sourcefiles attribute, and be aware
> that the sourcefiles attribute does NOT take wildcards, it has to be a
> comma separated list of source file names.
--
Larry V. Streepy, Jr.
Chief Technical Officer and VP of Engineering
Health Language, Inc. -- "We speak the language of healthcare"
970/626-5028 (office) mailto:streepy@healthlanguage.com
970/626-4425 (fax) http://www.healthlanguage.com
|