Jeffrey Jensen wrote:
>
> Yes they work perfectly. My examples are real - I copied them out of my
> build.xml file (and trimmed the extraneous).
well, when i asked "is this working", i was more referring my question
to the chap who started this thread.
> That is why I asked why you wrote a ne
Yes they work perfectly. My examples are real - I copied them out of my
build.xml file (and trimmed the extraneous).
That is why I asked why you wrote a new taskdef...Ant already provides
directory traversals for about everything. :-)
>>> [EMAIL PROTECTED] 03/12/02 01:52PM >>>
Jeffrey Jensen
Jeffrey Jensen wrote:
>
> Hmm, I'm not sure what you mean by "javadoc and packagenames don't take
> wildcards and don't do recursion".
well, "javadoc" the command-line program doesn't -- com.* means nothing to it.
I didn't know "javadoc" the Ant task did support that (or else i wouldn't
have wr
Hmm, I'm not sure what you mean by "javadoc and packagenames don't take
wildcards and don't do recursion".
A simple javac works like this:
and a simple javadoc works like this:
both using wildcards and recursion into direct
otisg wrote:
>
> Hello,
>
> I'm having trouble getting working here.
> It's complaining that I'm not specifying any packages nor classes:
>
> [javadoc] Generating Javadoc
> [javadoc] Javadoc execution
> [javadoc] usage: javadoc [options] [packagenames] [sourcefiles]
> [classnames] [@files]
> [j
--- otisg <[EMAIL PROTECTED]> wrote:
> I'm having trouble getting working here.
> It's complaining that I'm not specifying any packages nor classes:
[snip]
> However, I believe I am specifying them:
>
> sourcepath="${build.src}"
> destdir="${build.javadoc}"
> packagenames="com.*"
Does ${build.sr
Hello,
I'm having trouble getting working here.
It's complaining that I'm not specifying any packages nor classes:
[javadoc] Generating Javadoc
[javadoc] Javadoc execution
[javadoc] usage: javadoc [options] [packagenames] [sourcefiles]
[classnames] [@files]
[javadoc] javadoc: No packages or clas
