Author: wglass
Date: Mon Jan 2 02:43:03 2006
New Revision: 365328
URL: http://svn.apache.org/viewcvs?rev=365328view=rev
Log:
remove redundant constants
Modified:
jakarta/velocity/core/trunk/src/test/org/apache/velocity/test/MultipleFileResourcePathTestCase.java
Modified:
Author: wglass
Date: Mon Jan 2 04:42:18 2006
New Revision: 365339
URL: http://svn.apache.org/viewcvs?rev=365339view=rev
Log:
prevent NPE when velocimacro.library.autoreload=true and there is no global
velocimacro library
Modified:
[ http://issues.apache.org/jira/browse/VELOCITY-146?page=all ]
Will Glass-Husain updated VELOCITY-146:
---
Bugzilla Id: (was: 17669)
Summary: Macros not evaluated on the first attempt with #parse (was:
Macros not evaluated on the first
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta-velocity Wiki
for change notification.
The following page has been changed by WillGlassHusain:
http://wiki.apache.org/jakarta-velocity/FrontPage
Dear Wiki user,
You have subscribed to a wiki page or wiki category on Jakarta-velocity Wiki
for change notification.
The following page has been changed by WillGlassHusain:
http://wiki.apache.org/jakarta-velocity/MacroIssues
The comment on the change is:
new file
New page:
=== Macro bug
[
http://issues.apache.org/jira/browse/VELOCITY-277?page=comments#action_12361525
]
Will Glass-Husain commented on VELOCITY-277:
I added some thoughts on resolving this to the Wiki.
http://wiki.apache.org/jakarta-velocity/MacroIssues
macros
[
http://issues.apache.org/jira/browse/VELOCITY-146?page=comments#action_12361526
]
Will Glass-Husain commented on VELOCITY-146:
I added some thoughts on resolving this to the Wiki.
http://wiki.apache.org/jakarta-velocity/MacroIssues
Macros
I posted a little note about the JIRA issues on macros on the wiki
http://wiki.apache.org/jakarta-velocity/MacroIssues
Once I dug into these issues, I realized the scope of macros seems rather odd.
Specifically, various users have complained that you can't stick macros in a
file called by
First, happy new year to the Velocity developer community...
I've been pondering how Velocity handles exceptions. Right now, almost every
call to a plugin has a catch-all Exception handler which does little more than
log the Exception. There's been a couple of requests in the past few months
+1 on Option #3.
I think this is now accepted as a best practice with Java error handling.
regards Malcolm Edgar
On 1/3/06, Will Glass-Husain [EMAIL PROTECTED] wrote:
First, happy new year to the Velocity developer community...
I've been pondering how Velocity handles exceptions. Right now,
Hi Will,
+1 on Option #3.
I think this is now accepted as a best practice with Java error handling.
regards Malcolm Edgar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, 2006-01-03 at 08:18 +1100, Malcolm Edgar wrote:
+1 on Option #3.
I think this is now accepted as a best practice with Java error handling.
Yes, please... it would make life with Velocity a lot easier!
Regards,
Peter
PS: any ideas how I should torture students who handle exceptions
Author: wglass
Date: Mon Jan 2 17:18:13 2006
New Revision: 365508
URL: http://svn.apache.org/viewcvs?rev=365508view=rev
Log:
Fix typo in comments
Modified:
jakarta/velocity/core/trunk/src/java/org/apache/velocity/runtime/RuntimeConstants.java
Modified:
Author: wglass
Date: Mon Jan 2 17:22:48 2006
New Revision: 365509
URL: http://svn.apache.org/viewcvs?rev=365509view=rev
Log:
Updated change.xml file in maven format with all changes to date for
1.5. (in gradual preparation for 1.5 release). Moved changelog
for 1.4 and earlier to separate file.
Hi,
As it seems there's an emerging consensus we should move to a maven generated
site for the 1.5 release (keeping ant docs for personal documentation
generation), I've entered all 1.5 changes into a maven format changelog.
I like the format of the new changelog-- it's a bit more
[ http://issues.apache.org/jira/browse/VELOCITY-410?page=all ]
Will Glass-Husain resolved VELOCITY-410:
Resolution: Fixed
updated the maven change file. When we switch to a maven site this will be
well-structured and up-to-date
Revise
Hi,
Just a quick note on status to all interested parties. Progress continues in
fits and starts to the 1.5 release following the Road Map (but having missed
the target dates). I'd hoped to have my tasks done last month but an overload
of project work wore me down (multiple simultaneous
17 matches
Mail list logo
