0.16... I had the same thought at first, but I checked and the
filenames do *contain* .java, but they end with .svn-base, etc. Maybe
javadoc is getting tripped up because the filenames contain .java,
which is definitely a javadoc bug.
I just tried running with -verbose. In the case of the 'svn export'
tree, the verbose output shows "Loading source files for package ..."
followed by messages about parsing all the files in that package. In
the 'svn co' tree, it only shows the "Loading source files for package"
message for the topmost directory containing src. After it says
"Constructing Javadoc information", it parses some of the files in the
deeper directories, presumably following references to those classes
from the classes in the package that was parsed. Seems strange.
Maybe ROT-13'ing the filenames under the .svn directory would do the
On Sunday, January 5, 2003, at 12:34 PM, Peter Davis wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Sunday 05 January 2003 12:23, Rob Clark wrote:
>> The problem doesn't
>> occur if I 'svn export', so I'm assuming that javadoc is getting
>> tripped up over something in the .svn directories.
> What version of svn are you using? Not too long ago, the text-base
> in .svn/ used the same filenames as the actual files, ie., they would
> with ".java" and trip up tools that looked for "*.java". Now they
> have an
> ".svn-base" extension.
> The change was intended to solve exactly that type of problem. If your
> .svn/ directory contains ".java", then upgrade and see if it still
> work. If not, then, um, we'll have to figure this out. For starters,
> the "-verbose" flag to javadoc and see if you can glean something, or
> the output here.
> - --
> Peter Davis
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.7 (GNU/Linux)
> -----END PGP SIGNATURE-----
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Sun Jan 5 23:52:59 2003