[
https://issues.apache.org/jira/browse/VELOCITY-789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12966891#action_12966891
]
Adrian Tarau commented on VELOCITY-789:
---------------------------------------
For a library that has ~500kb bringing another 500kb for a few classes it's
just ... not optimal. Don't get me wrong I am not against using great code in
Velocity but this days it is very common to shade libraries to reduce the
size and avoid version conflicts(include only what you use).
Since Velocity is moving to Maven, Maven Shade Plugin(
http://maven.apache.org/plugins/maven-shade-plugin) can be used to include(and
relocate) any class dependencies.
The only disadvantage I would see is to get bug reports for classes that are
not Velocity specific(but since those classes will be relocated under
org.apache.velocity it will look like they are developed as part of Velocity
project), but I think this would not happen to often.
> Reorganize dependencies in Velocity Engine Core
> -----------------------------------------------
>
> Key: VELOCITY-789
> URL: https://issues.apache.org/jira/browse/VELOCITY-789
> Project: Velocity
> Issue Type: Bug
> Reporter: Antonio Petrelli
> Assignee: Antonio Petrelli
>
> Currently Velocity Engine core depends on:
> Commons Lang
> Commons Collections
> Avalon LogKit
> Apache Jakarta ORO
> LogKit and ORO should be removed, as they are obsolete. Commons Lang and
> Collections should be replaced or shaded.
--
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]
