[
https://issues.apache.org/jira/browse/VELOCITY-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nathan Bubna resolved VELOCITY-744.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.7
Sounds like a perfectly reasonable thing to log for debugging. Not sure why it
went away. Now it's back.
> No more VM adding logs
> ----------------------
>
> Key: VELOCITY-744
> URL: https://issues.apache.org/jira/browse/VELOCITY-744
> Project: Velocity
> Issue Type: Bug
> Components: Engine
> Affects Versions: 1.6.2
> Reporter: Alexandre Garnier
> Priority: Minor
> Fix For: 1.7
>
>
> org.apache.velocity.runtime.VelocimacroFactory.addVelocimacro(String, String,
> String[], String) add a log "added <VMName> : source = <VMBody>"
> The new 1.6 method
> org.apache.velocity.runtime.VelocimacroFactory.addVelocimacro(String, Node,
> String[], String) no more log this.
> The first one is used by
> org.apache.velocity.runtime.RuntimeInstance.addVelocimacro(String, String,
> String[], String) which is now deprecated for
> org.apache.velocity.runtime.RuntimeInstance.addVelocimacro(String, Node,
> String[], String) which use the new VelocimacroFactory.addVelocimacro
> This logs was usefull for debug.
--
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: [email protected]
For additional commands, e-mail: [email protected]
