Traits in Groovy comes as a good replacement to Java's interfaces and,
in particular Java 8's interfaces that features default methods. Though,
while working on a project in Groovy, I've come across a
counter-intuitive and (AFAIK) undocumented limitation of traits: inner
traits and access to en
>
> I agree with Cédric.
> It'd be better to integrate the actual tips in the JavaDocs per se.
> Furthermore, the Groovy's GroovyDoc can also contain code samples that are
> actually tested, with assertions.
> So not only would that improve the documentation itself, without going
> through another
was thinking of the same problem with our http://gpars.website. Do we
include code samples or not ? or only links to external sites ? i like the
idea of "live" code fragments within the doc.s that are compiled/tested as
a part of document generation. this guarantees that code in our docs works
as
I think it is better to have very complete documentation at GroovyDoc level,
without the need to follow external links. My experience with the Ratpack
Javadoc documentation is that with all example code and snippets included at
Javadoc level that it is very easy to use as reference.
It is no prob
