Author: wglass
Date: Fri Sep 23 23:04:39 2005
New Revision: 291256
URL: http://svn.apache.org/viewcvs?rev=291256view=rev
Log:
check to see if Velocity was initialized and give meaninful exception message
if not. VELOCITY-374
Modified:
Will Glass-Husain [EMAIL PROTECTED] writes:
I was wondering whether it would be a good idea to actually remove the
machine built files from the source tree and just rebuild them on the
fly when generating the jar.
There are sometimes users that patch these files and then we have to
tell them
Daniel L. Rall dlr@finemaltcoding.com writes:
On Thu, 22 Sep 2005, [EMAIL PROTECTED] wrote:
Author: henning
Date: Thu Sep 22 06:32:34 2005
New Revision: 290942
URL: http://svn.apache.org/viewcvs?rev=290942view=rev
Log:
- Clean up imports using Eclipse
- Remove trailing blanks
This type
Will Glass-Husain (JIRA) [EMAIL PROTECTED] writes:
Asked about this on dev list - no comments. Thus blessed by the power of lazy
consensus - committed.
While I agree with your patch, you might actually give us a bit more
time. I was away from my mail for just a day. ;-)
Best regards
Dan,
I think this type of activity is rare but needs to occur in the short term.
There's some new momentum to clean up the code base, fix the outstanding
bugs, and issue a release. Moving the test cases out of the main jar into a
separate class has been discussed on the dev list a few times.
I was browsing the newly organized test tree. There's a class there
org.apache.velocity.test.misc.Test that looks archaic. Anyone ever use this?
I suspect it's a pre-junit test run from the command line. As long as we're
cleaning stuff up, I think we should delete it. (Henning, in