You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/05/01 19:03:40 UTC
[jira] Commented: (MEV-385) velocity-dep 1.4 should be relocated to
velocity 1.4
[ http://jira.codehaus.org/browse/MEV-385?page=comments#action_64491 ]
Carlos Sanchez commented on MEV-385:
------------------------------------
I think that velocity-dep must be kept as is. If somebody decides to use it, it's ok for them. the real issue is MEV-384
> velocity-dep 1.4 should be relocated to velocity 1.4
> ----------------------------------------------------
>
> Key: MEV-385
> URL: http://jira.codehaus.org/browse/MEV-385
> Project: Maven Evangelism
> Type: Bug
> Reporter: fabrizio giustina
>
>
> After fixing MEV-384 (velocity 1.4 dependencies) velocity-dep 1.4 should be relocated to velocity 1.4.
> Velocity-dep-1.4.jar is the same as velocity-1.4.jar PLUS logkit, oro and commons-collections packaged together. Since maven already manages transitive dependencies it makes no sense providing a single jar with everything packaged together for easier deploy.
> Now projects always end up having two copies of the velocity jars in the classpath (velocity and velocity-dep are usually both included in dependencies).
> Even worse, your project may depend on a specific version of oro or logkit, newer than the one in the velocity-dep jar: in that case you will end up having two different versions of those libraries in the classpath, one of them hidden in the velocity-dep jar (and so very difficult to detect). That could cause nasty problems, and maven can't help in selecting only the version you really need in your project...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira