You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2010/12/07 20:31:29 UTC

For 5.3: extend JavaDoc, eliminate ComponentReport

I've been thinking that it would be nice, for 5.3, to get rid of the
ComponentReport and create a new javadoc plugin that encoded the paramter
(and examples) directly into the Javadoc.  I think this would make
it easier to generate component documentation for non-Maven (Ant, Gradle,
etc.) projects.

-- 
Howard M. Lewis Ship

Creator of Apache Tapestry

The source for Tapestry training, mentoring and support. Contact me to learn
how I can get you up and productive in Tapestry fast!

(971) 678-5210
http://howardlewisship.com

Re: For 5.3: extend JavaDoc, eliminate ComponentReport

Posted by Igor Drobiazko <ig...@gmail.com>.

What kind of javadoc plugin are you talking about? I guess we need an
abstraction/replacement for the Sink API.

On Tue, Dec 7, 2010 at 8:31 PM, Howard Lewis Ship <hl...@gmail.com> wrote:

> I've been thinking that it would be nice, for 5.3, to get rid of the
> ComponentReport and create a new javadoc plugin that encoded the paramter
> (and examples) directly into the Javadoc.  I think this would make
> it easier to generate component documentation for non-Maven (Ant, Gradle,
> etc.) projects.
>
> --
> Howard M. Lewis Ship
>
> Creator of Apache Tapestry
>
> The source for Tapestry training, mentoring and support. Contact me to
> learn
> how I can get you up and productive in Tapestry fast!
>
> (971) 678-5210
> http://howardlewisship.com
>



-- 
Best regards,

Igor Drobiazko
http://tapestry5.de