ctually works but I
> don't think it'd terribly difficult. Any thoughts, hints, suggestions?
>
> /bill
>
> -Original Message-----
> From: streepy [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 12:09 PM
> To: ant-user
> Cc: streepy
> Subject: Re:
o:[EMAIL PROTECTED]]
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 sourcefil
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 separate
> > packagenames="**/.*"
>
> It works (Larry's packagenames with wild cards
I verified that only the packages got the docs prepared, not the application
(the ones not belonging to a package)
How do I javadoc those too, and the packages as well.
thks
Unfortunately on this one I had to read the source code. The wildcard
(which has to end in .*) is converted to a fileset patter by converting
all '.' to '/' and appending a '*' to the end. So, my pattern ends up
as a fileset includes="**//**", which matches every package.
However, by looking at
> > Is "stp" the actual name of your package? The example in the doc shows:
> > > ...
> > So I would guess you need to specify the actual package name and
terminate
> > it with a wildcard -- eg: com.foo.stp.*
>
> No it's not. Actually, it's a group of 3 applications, and 2 packages, all
> u
> Is "stp" the actual name of your package? The example in the doc shows:
> ...
> So I would guess you need to specify the actual package name and terminate
> it with a wildcard -- eg: com.foo.stp.*
No it's not. Actually, it's a group of 3 applications, and 2 packages, all
under the same
com.cyberplus.util,
>com.cyberplus.le.*"/>
>
> -Original Message-
> From: Larry V. Streepy, Jr. [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 20, 2001 1:53 PM
> To: [EMAIL PROTECTED]
> Subject: Re: javadoc help
:[EMAIL PROTECTED]]
Sent: Wednesday, June 20, 2001 1:53 PM
To: [EMAIL PROTECTED]
Subject: Re: javadoc help
In my build, I didn't need to specify a wild card. Here are two forms
that I use in our build:
and
Diane Holt wrote:
>
> Is "stp" the actual name of your
In my build, I didn't need to specify a wild card. Here are two forms
that I use in our build:
and
Diane Holt wrote:
>
> Is "stp" the actual name of your package? The example in the doc shows:
> ...
> So I would guess you need to specify the actual package name and terminat
Just to eliminate the basics here, does the first line of code begin
with
package stp;
or
package stp[.*];
where [.*] indicates optional sub-package stuff?
If the latter is true, then you need to change packagenames="stp.*"
As an aside, I shudder to see that title (no knock on Pinar.)
-
Is "stp" the actual name of your package? The example in the doc shows:
wrote:
> I'm trying to understand how to make work.
>
> 1. I tried packagenames="..." (pretty much copied from the manual)
>
> packagenames="stp" sourcepath="/stp"
> classpathref="classpath" (<-- this on
Suu Quan wrote:
> I'm trying to understand how to make work.
> 1. I tried packagenames="..." (pretty much copied from the manual)
> packagenames="stp" sourcepath="/stp"
[...]
> I got as output
> doc:
> [javadoc] Generating Javadoc
> [javadoc] Javadoc execution
> [javadoc] javadoc
13 matches
Mail list logo
