Hi,
excuse me for being anal but while starting to think about preparing
beta2, I noticed that we introduced quite a number of problems in the
javadocs.
(Nathan: As you were asking whether the large amount of formal javadoc
fixes had any real impact: Yes. Due to these fixes, it was now easy to
Thanks,
That's what happens when you keep tinkering with the code before committing.
Anyone suggest a good plugin (or setting) in Eclipse to catch these
javadoc issues ahead of time?
On a separate topic, I was going to write an email about beta2. Shall
we call for a vote soon? What else do
with the code before committing.
Anyone suggest a good plugin (or setting) in Eclipse to catch these
javadoc issues ahead of time?
On a separate topic, I was going to write an email about beta2. Shall
we call for a vote soon? What else do we want to fix before then?
(be nice to highlight this when we
Incidentally,
(in case anyone else is interested). It turns out there's a setting
in Eclipse under Compiler/Javadoc that flags a warning for every
Javadoc problem. You can set this by project so that your code
without the rigid Velocity style scrutiny can stay in more relaxed
form.
WILL v^-
