You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Will Glass-Husain (JIRA)" <ji...@apache.org> on 2005/09/18 22:46:54 UTC
[jira] Updated: (VELOCITY-277) macros in #parsed files are not refreshed when including page is refreshed
[ http://issues.apache.org/jira/browse/VELOCITY-277?page=all ]
Will Glass-Husain updated VELOCITY-277:
---------------------------------------
Bugzilla Id: (was: 29959)
Fix Version: 1.5
Description:
If a template #parses a file containing velocimacros, changes those macros do
not make it into the including template. This is true whether the file is
included via the library property or via #parse.
Although there is the velocimacro.library.autoreload property, it is "not for
use in production" according to the documentation - and cannot be used with
template caching.
Also, often, macros included via #parse do not pick up their macros the first
time they are compiiled. And with template caching they are only ever called
once, this leads to situations where changes in templates that include macros
and are cached do not function in production.
was:
If a template #parses a file containing velocimacros, changes those macros do
not make it into the including template. This is true whether the file is
included via the library property or via #parse.
Although there is the velocimacro.library.autoreload property, it is "not for
use in production" according to the documentation - and cannot be used with
template caching.
Also, often, macros included via #parse do not pick up their macros the first
time they are compiiled. And with template caching they are only ever called
once, this leads to situations where changes in templates that include macros
and are cached do not function in production.
Environment:
Operating System: other
Platform: Other
was:
Operating System: other
Platform: Other
Assign To: (was: Velocity-Dev List)
Commenting on this old bug...
I think the semantics of "velocimacro.library.autoreload" are clear. The real problem is your statement that "macros included via #parse" are not picked up. If this is fixed, I think you'd be ok.
I know it's been a while, but can you supply a test case for this?
> macros in #parsed files are not refreshed when including page is refreshed
> --------------------------------------------------------------------------
>
> Key: VELOCITY-277
> URL: http://issues.apache.org/jira/browse/VELOCITY-277
> Project: Velocity
> Type: Bug
> Components: Build
> Versions: 1.4
> Environment: Operating System: other
> Platform: Other
> Reporter: Tim White
> Priority: Critical
> Fix For: 1.5
>
> If a template #parses a file containing velocimacros, changes those macros do
> not make it into the including template. This is true whether the file is
> included via the library property or via #parse.
> Although there is the velocimacro.library.autoreload property, it is "not for
> use in production" according to the documentation - and cannot be used with
> template caching.
> Also, often, macros included via #parse do not pick up their macros the first
> time they are compiiled. And with template caching they are only ever called
> once, this leads to situations where changes in templates that include macros
> and are cached do not function in production.
--
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: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org