You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Claude Brisson (JIRA)" <ji...@apache.org> on 2016/07/15 13:46:20 UTC

[jira] [Closed] (VELOCITY-716) Configuring VelocityEngine used by DVSL

     [ https://issues.apache.org/jira/browse/VELOCITY-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claude Brisson closed VELOCITY-716.
-----------------------------------
    Resolution: Won't Fix

This is a DVSL issue, not a Velocity Issue. Feel free to open a related bug in DVSL. But DVSL has been deprecated, and is unlikely to see another release.

> Configuring VelocityEngine used by DVSL
> ---------------------------------------
>
>                 Key: VELOCITY-716
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-716
>             Project: Velocity
>          Issue Type: Improvement
>          Components: DVSL
>    Affects Versions: 1.6.1
>            Reporter: Nikita Salnikov-Tarnovski
>
> From the DVSL code we read that only the following VelocityEngine configuration parameters are supported:
>      *  <li>VM_LIBRARY</li>
>      *  <li>FILE_RESOURCE_LOADER_PATH</li>
>      *  <li>RUNTIME_LOG</li>
>      *  <li>RUNTIME_LOG_LOGSYSTEM</li>
>      *  <li>RUNTIME_LOG_LOGSYSTEM_CLASS</li>
> Which means, among other things, that there are no posibility to use ResourceLoader other than default FileSystem. We use DVSL in web application, so filesystem is not the most confinient source of resources for us. Why cannot I use ClasspathResourceLoader?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org