[ 
https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798616#action_12798616
 ] 

Christoph Reck commented on VELOCITY-617:
-----------------------------------------

I suggest to deprecate org.apache.velocity.convert.WebMacro, since it was an 
utility to migrate from it in early days when the clean room re-implementation 
was made. 
Now WM has changed a lot and I believe this class file is not useful any more.

> Jakarta Commons ORO at runtime
> ------------------------------
>
>                 Key: VELOCITY-617
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-617
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.5, 1.6
>            Reporter: Adrian Tarau
>            Priority: Minor
>             Fix For: 1.7
>
>         Attachments: velocity-617.patch
>
>
> There is a misleading information on the dependency 
> page(http://velocity.apache.org/engine/releases/velocity-1.5/dependencies.html
>  , These dependencies are required to compile and run the application) about 
> oro.
> "The most common case is the integration of the Velocity runtime into your 
> application. In this case, you must add commons-collections, commons-lang and 
> oro to your application (and optional logging if required). If you already 
> have one or more of these libraries in your application, you should check if 
> you need to update their versions. "
> also
> "These dependencies are required to compile and run the application"
> Except if Velocity is configured to escape references, oro is not need it at 
> runtime, only at compile time(most of the users don't care about compile 
> time).

-- 
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]

Reply via email to