Bernhard Huber wrote:
>
> hi, nikola
>
> >>adding some javadoc tags in orde to generate reference documentation.
> >>
> >
> >I think it's super! :-)
Me too.
> >It would be nice if also xsl stylesheets have this feature; IIRC some
> >taglibs
> >already do.
there is something called xsldoc but never used it. Anybody here did?
> >Just one thing: in the examples you posted, there is ErrorNotifier which is
> >deprecated; IMHO it could be skipped entirely or put in a special
> >deprecated section.
> >
> Well i just walk over all javasources, if
> java class extends org.apache.cocoon.generation.Generator i will
> include this class
> to the ref-doc in order to mark it as deprecated we have to add
> a @cocoon:deprectated javadoc-tag than in generated ref-doc
> a row sitemap-useag: deprecated could be generated.
>
> But as mentioned already the community have to accept adding
> javadoc-tags to the
> java sources.
> Perhaps let's see what other developers have to say....
I have no problems about having cocoon-specific javadoc tags (if
properly namespaced like @cocoon:deprecated which is what you are
proposing, so I'm cool) but what I would really want is a doclet that
outputs XML that we could later incorporate seemlessly with our
documentation!
What I don't like about javadocs is that they appear 'coherent' in
between them, but look 'incoherent' with the rest of the documentation
(unless you took the very poor choice of documenting your stuff
*uniquely* from the javadocs, which is a bad thing to do IMO)
Whad do you think?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
