[jira] Reopened: (VELOCITY-423) Report invalid references

2006-11-01 Thread Henning Schmiedehausen (JIRA)
[ http://issues.apache.org/jira/browse/VELOCITY-423?page=all ] Henning Schmiedehausen reopened VELOCITY-423: - The following Javadoc Issues were introduced by the patches related here. As Javadocs are currently the most important

Javadoc issues

2006-11-01 Thread Henning P. Schmiedehausen
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

svn commit: r469919 - in /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime: VelocimacroFactory.java log/Log.java

2006-11-01 Thread henning
Author: henning Date: Wed Nov 1 06:35:46 2006 New Revision: 469919 URL: http://svn.apache.org/viewvc?view=revrev=469919 Log: Fix javadoc issues. Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime/VelocimacroFactory.java

Re: Javadoc issues

2006-11-01 Thread Will Glass-Husain
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

Re: Javadoc issues

2006-11-01 Thread Henning Schmiedehausen
Hehe, two minds thinking alike. I wanted to do some issue trawling today (public holiday in Germany) but relatives came by for visiting, so I didn't get much done... However, I do think we are basically done with all serious issues (there are a number of old thinks like VELOCITY-24 for which I

POLL - release beta 2?

2006-11-01 Thread Will Glass-Husain
Hi, I think we should release a beta 2 version of Velocity allowing users to test out the recent spurt of bug fixes and improvements. You can see a report on improvements made during the recent Hackathon at these links: http://www.mail-archive.com/velocity-dev@jakarta.apache.org/msg15131.html

svn commit: r470254 - /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime/parser/node/MathUtils.java

2006-11-01 Thread wglass
Author: wglass Date: Wed Nov 1 23:14:00 2006 New Revision: 470254 URL: http://svn.apache.org/viewvc?view=revrev=470254 Log: fixed javadocs for random file Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime/parser/node/MathUtils.java Modified:

svn commit: r470256 - in /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/app/event: ./ implement/

2006-11-01 Thread wglass
Author: wglass Date: Wed Nov 1 23:20:36 2006 New Revision: 470256 URL: http://svn.apache.org/viewvc?view=revrev=470256 Log: VELOCITY-423. Cleaned up Javadocs. Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/app/event/EventCartridge.java

svn commit: r470261 - in /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/util/introspection: ClassMap.java MethodMap.java SecureIntrospectorControl.java SecureIntrospectorImpl.java SecureU

2006-11-01 Thread wglass
Author: wglass Date: Wed Nov 1 23:32:37 2006 New Revision: 470261 URL: http://svn.apache.org/viewvc?view=revrev=470261 Log: Apply javadoc fixes. VELOCITY-475. Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/util/introspection/ClassMap.java

Re: Javadoc issues

2006-11-01 Thread Will Glass-Husain
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^-

[jira] Resolved: (VELOCITY-475) Javadocs for SecureUberspector are not correct.

2006-11-01 Thread Will Glass-Husain (JIRA)
[ http://issues.apache.org/jira/browse/VELOCITY-475?page=all ] Will Glass-Husain resolved VELOCITY-475. Resolution: Fixed fixed Javadocs for SecureUberspector are not correct. ---

[jira] Resolved: (VELOCITY-423) Report invalid references

2006-11-01 Thread Will Glass-Husain (JIRA)
[ http://issues.apache.org/jira/browse/VELOCITY-423?page=all ] Will Glass-Husain resolved VELOCITY-423. Resolution: Fixed excellent point. cleaned them all up. Report invalid references - Key:

svn commit: r470263 - /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime/parser/node/ASTSetDirective.java

2006-11-01 Thread wglass
Author: wglass Date: Wed Nov 1 23:37:15 2006 New Revision: 470263 URL: http://svn.apache.org/viewvc?view=revrev=470263 Log: fix Javadocs Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/runtime/parser/node/ASTSetDirective.java Modified:

svn commit: r470265 - /jakarta/velocity/engine/trunk/src/java/org/apache/velocity/app/event/implement/ReportInvalidReferences.java

2006-11-01 Thread wglass
Author: wglass Date: Wed Nov 1 23:45:02 2006 New Revision: 470265 URL: http://svn.apache.org/viewvc?view=revrev=470265 Log: fix formatting typo in class javadoc Modified: jakarta/velocity/engine/trunk/src/java/org/apache/velocity/app/event/implement/ReportInvalidReferences.java Modified: