ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthieu Bentot <>
Subject RE: [PATCH] 1.5Beta1: Javadoc doesn't set the sourcepath
Date Fri, 10 May 2002 15:35:07 GMT
> -----Original Message-----
> From: Stefan Bodewig []
> Sent: Friday, May 10, 2002 4:25 PM
> To:
> > In 1.5Beta1, Javadoc doesn't add the sourcepath value to the javadoc
> > command line.
> It does, but only if (1) you have specified packages to document and
> (2) the referenced directories actually hold .java files for the
> packages you want to document.
> > AFAIK, it instead build the sourcepath from the files.
> It does so in addition to the specified sourcepath.


> > This breaks other tools that rely on Javadoc's behavior to (try to)
> > load dependencies files, even if it doesn't generate doc for them
> > (namely, xdoclet).
> Which dependency files may that be?

ejbdoclet generate home/remote interfaces, deployment descriptors and so on
from a single class using custom tags. To do so, it identifies what's a bean
by looking at the interfaces. So if your bean class extends a generic
adapter class, it needs to look at this one, but can't if it can't be

> I've made the change because of this snippet from JDK 1.3's javadoc
> documetation:
> : Note that you can use the -sourcepath option only when passing
> : package names into the javadoc command
> So, no package names, no -sourcepath.

Ack that, but the doc is a bit unclear, it follows on saying 'it will not
locate .java files passed into the javadoc command'. Okay. But the
implementation will for files that are not passed to javadoc. And the doc
doesn't quite say it won't for those.

> In what situation is Ant's current code ommitting stuff that you need?

See above.
Okay it's more like an incompatibility between ant1.5 and xdoclet (it relies
on the old you-got-what-you-asked-for behavior).




To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message