[ http://issues.apache.org/jira/browse/VELOCITY-440?page=comments#action_12413461 ]
Henning Schmiedehausen commented on VELOCITY-440: ------------------------------------------------- I am not sure that I understand this request. There is no such thing as a "TEMPLATE_ROOT". Velocity templates are loaded through a set of loaders that you configure in your properties. For each directory that you want to use, you configure a FileResourceLoader. For the Classpath, you configure a ClasspathResourceLoader. A template is not necessary the same thing as a file. Most of the times, a template is loaded from a file but that is done in a resource loader. This BTW is IMHO a question for the dev/users list, not an issue in JIRA. :-) > Make TEMPLATE_ROOT behave more like classpath...that is a list of directories > to search. > ---------------------------------------------------------------------------------------- > > Key: VELOCITY-440 > URL: http://issues.apache.org/jira/browse/VELOCITY-440 > Project: Velocity > Type: Improvement > Components: Build > Versions: 1.4 > Environment: WindowsXP > Reporter: Colbert Philippe > Priority: Blocker > > I want to use Velocity as a standard preprocessor for many programming > languages or configuration files. By using it this way, I can build a > library of Velocity macros that I can callup whenever I want. I want to be > able to have macros located in different directories. So the TEMPLATE_ROOT > should be a list of directories that is searched by Velocity to find the > first macro file needed. > There also a need to have some macros archived in the Jar. So a unified > solution for having macros dispersed in a list of directories and insided the > JAR file (in the real classpath). > This would go a long way to improve Velocity. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
