Hi,
in Trinidad we only publish the javadoc for API-based classes and not
for impl-specific ones.
MyFaces core is currently delivering in the assembled stuff both, API and IMPL.
What do we want to do ?
--
Matthias Wessendorf
further stuff:
blog: http://matthiaswessendorf.wordpress.com/
mail:
I don't feel Trinidad should have to document IMPL related code just because
the core does. I also don't think we should stop documenting core because
Trinidad only documents the API based code.
Dennis Byrne
On 7/14/07, Matthias Wessendorf [EMAIL PROTECTED] wrote:
Hi,
in Trinidad we only
no,
not because of trinidad.
My point was that it might be *cleaner* to not publish impl doc,
I don't have a strong feeling on this one, to be honest. I just
remembered, when I was looking at the MyFaces 1.2.0 out-of-date
assembly :-)
-Matthias
On 7/14/07, Dennis Byrne [EMAIL PROTECTED] wrote:
Definitely, no one here has to do anything. :) The question
is whether delivering Javadoc for the IMPL is one the
whole a good or bad thing... Someone who is an active
developer on MyFaces can, of course, easily run javadoc
on their own.
IMO, the target of Javadoc in distributions is the
