I think it's not...
If I remember well then when the components of a library are enumerated,
only those components are listed which have an explicit <component-type
/> declaration in the .library file. Pure Java components are not, so
they won't be included in the documentation by default. Pure Java
components should be explicitly declared as part of the library in an
XML file named LibraryName.library.tapdoc.
Similar possibility is given for components, in a
ComponentName.jwc.tapdoc file one could define additional component
information, like visual sample, example codes, etc.
I haven't documented the format of these XML files yet, but I would... :)
But of course annotations are supported and parameter descriptions are
extracted from the .java file (if available) using a custom javadoc doclet.
Regards,
Norbi
andyhot wrote:
Henri Dupre wrote:
Oh this looks very nice!
Does tapdoc take into account also components with annotations that
have no
.jwc?
It does... I think it uses a custom doclet to extract javadocs from
those 'annotation-only'
components
On 8/15/06, Norbert Sándor <[EMAIL PROTECTED]> wrote:
Hello,
I have converted Tapdoc to Maven2, so it now has a standard website at:
http://www.erinors.com/developer/project/tapdoc/
The jar and the source code is available from our maven2 repository.
You can download a Maven2-based demo application from the website as
well.
(Please note:
- the Maven2 integration is partial, currently the ant-plugin is used to
integrate tapdoc to maven-based projects
- the source code needs further cleanup)
Regards,
Norbert Sándor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
