"Robert Larsen" <Xrcl@ttpcom.com> wrote in message
news:b6hjlf$gpa$1@sunsite.dk...
> Jeg er ikke helt sikker, men det mener jeg ikke, at du kan med JavaDoc.
> Du kan derimod bruge Doxygen (
http://www.stack.nl/~dimitri/doxygen/),
> som er et lidt bredere anvendeligt dokumenteringsværktøj. Det kan læse
> JavaDoc syntax og tilføjer en fandens masse andet også, og kan også
> dokumentere andre programmeringssprog. Det konfigureres med en projekt
> specifik konfigureringsfil (som kan genereres med et grafisk værktøj),
> og der kan man specificere lister over filer, som ikke skal dokumenteres.
>
> VH
>
> Robert
Tak det prøver jeg - i øvrigt har du ret ... jeg fandt nedenstående.
Mvh. Morten
A15. How can I exclude certain public members or classes from being
documented? Often you need to make a method public so that it can be
accessible from other packages, not because you want it to be part of the
public API. Having these methods appear in the documentation merely confuses
application developers. There is currently no Javadoc option to hide,
exclude or suppress public members from the javadoc-generated documentation.
If you want to exclude public classes or interfaces, you can do so by
passing into javadoc only the source filenames for all classes you want to
document, and exclude those you want to omit. Notice this has the
granularity of files, not classes. (You can put the list of classes in a
command line argument file rather than directly on the command line.)
Javadoc offers no way to omit classes when passing in package names on the
command line. We are considering @exclude as a proposed tag for excluding
members.