You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Adrian Tarau (JIRA)" <de...@velocity.apache.org> on 2008/09/26 15:33:44 UTC
[jira] Created: (VELOCITY-617) Jakarta Commons ORO at runtime
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
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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798811#action_12798811 ]
Nathan Bubna commented on VELOCITY-617:
---------------------------------------
Yeah, WebMacro is already gone in 2.x. I'll mark it deprecated in the trunk.
Also, the 2.x branch should really drop ORO and just the jdk regex stuff, if anyone wants to patch that.
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna updated VELOCITY-617:
----------------------------------
Fix Version/s: 1.7
Rest of the fix will probably wait until after 1.6 is released.
> 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.6, 1.7
>
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna updated VELOCITY-617:
----------------------------------
Fix Version/s: (was: 1.6)
> 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
>
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Christoph Reck (JIRA)" <de...@velocity.apache.org>.
[ 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648249#action_12648249 ]
Nathan Bubna commented on VELOCITY-617:
---------------------------------------
I can change the more prominently linked dependency file:
http://velocity.apache.org/engine/devel/jar-dependencies.html
But this one is entirely Maven produced:
http://velocity.apache.org/engine/devel/dependencies.html
I don't know how to change the POM to have Maven display the proper info there. There's more that's wrong on that page than just the stuff about Oro.
> 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.6
>
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Resolved: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna resolved VELOCITY-617.
-----------------------------------
Resolution: Fixed
Fix Version/s: 2.0
Resolved as it's going to get for now...
> 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, 2.0
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Adrian Tarau (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Tarau updated VELOCITY-617:
----------------------------------
Priority: Minor (was: Major)
> 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
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Jarkko Viinamäki (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarkko Viinamäki updated VELOCITY-617:
--------------------------------------
Attachment: velocity-617.patch
This patch marks ORO dependency as optional (which is I guess the only possible way to mark this kind of dependency). AFAIK there is no way to change the text on the Maven generated dependencies.html page.
ORO is only used by this runtime class:
org.apache.velocity.app.event.implement.EscapeReference
So if that handler is not used, ORO is not needed during runtime. This patch also updates Velocity Developer Guide.
During compile time ORO is obviously needed and there are two other classes that use ORO:
org.apache.velocity.test.BaseTestCase
org.apache.velocity.convert.WebMacro
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Updated: (VELOCITY-617) Jakarta Commons ORO at runtime
Posted by "Nathan Bubna (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Bubna updated VELOCITY-617:
----------------------------------
Fix Version/s: 1.6
> 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.6
>
>
> 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: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org