You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Barrie Treloar (JIRA)" <ji...@apache.org> on 2008/06/13 02:52:45 UTC

[jira] Created: (TEXEN-16) Allow any VelocityEngine. property to be configured via TexenTask

Allow any VelocityEngine. property to be configured via TexenTask
-----------------------------------------------------------------

                 Key: TEXEN-16
                 URL: https://issues.apache.org/jira/browse/TEXEN-16
             Project: Texen
          Issue Type: Improvement
    Affects Versions: 1.0
            Reporter: Barrie Treloar


org.apache.velocity.runtime.RuntimeConstants contains ways to configure the VelocityEngine.

The Texen Task 1.0 currently only supports the following constants:

RuntimeConstants.FILE_RESOURCE_LOADER_PATH
VelocityEngine.RESOURCE_LOADER,
"classpath." + VelocityEngine.RESOURCE_LOADER + ".class"
"classpath." + VelocityEngine.RESOURCE_LOADER + ".cache"
"classpath." + VelocityEngine.RESOURCE_LOADER + ".modificationCheckInterval",
RuntimeConstants.RUNTIME_LOG

I'd like to be able to separate out my Velocimacros into individual files.
But to do that I think I need to set VM_LIBRARY which I can not do through texen.

Would it be possible to add a general purpose VelocityEngine option property to the TexenTask so that anything that needs to be configured can be?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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