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 we want to fix before then?
(be nice to highlight this when we launch the TLP site).
WILL
On 11/1/06, Henning P. Schmiedehausen <[EMAIL PROTECTED]> wrote:
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
spot that the number of problems went up. That wasn't possible when
the number to start with was already very large because then the real
issues would have been lost in the noise.)
I've reopened VELOCITY-423 and opened VELOCITY-475 to deal with these
problems (Will, I'm afraid that will be mostly work for you...)
Best regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
RedHat Certified Engineer -- Jakarta Turbine Development -- hero for hire
Linux, Java, perl, Solaris -- Consulting, Training, Development
Social behaviour: Bavarians can be extremely egalitarian and folksy.
-- http://en.wikipedia.org/wiki/Bavaria
Most Franconians do not like to be called Bavarians.
-- http://en.wikipedia.org/wiki/Franconia
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Forio Business Simulations
Will Glass-Husain
[EMAIL PROTECTED]
www.forio.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
