The most common way, I would think, to suppress the generation of Javadocs for inner classes is with access specifiers on the classes themselves and at generation time with Javadoc. If the inner class is not part of the public API (which you want to Javadoc), then why make it public?
-Matt --- Ritesh Trivedi <[EMAIL PROTECTED]> wrote: > Hi, > > I have tried looking at the mailing list since past > 24 hrs to find answer to this, but no success. Sorry > for the bandwidth ahead of time. > > I have a situation where I need to generate javadocs > for the subset of the source directory which > contains java source files which should be exposed > via Javadocs. > > What I do currently is, I copy only those files > which I want javadocs generated for to a temp > directory and call javadocs task from my build.xml > on that temp source directory. But the problem with > this approach is, its generating javadocs for files > that I didnt ask it to!! I think its picking those > extra classes up from the classpath!! On top of that > its generating javadocs for the innner classes too! > which I dont want. > > Another thing I tried was to put a fileset inside > the javadoc task and exclude the files which I dont > want, still its generating more files than I ask it > to! > > Does anyone know a better way of doing this? > > Thanks > > Ritesh > > ================================ > Ritesh Trivedi > Embrace Networks > 408-585-5621 __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
