You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@velocity.apache.org by "Vincent Massol (JIRA)" <ji...@apache.org> on 2006/11/11 11:57:37 UTC
[jira] Created: (VELOCITY-491) Velocity-dep repackages the Jakarta
ORO classes
Velocity-dep repackages the Jakarta ORO classes
-----------------------------------------------
Key: VELOCITY-491
URL: http://issues.apache.org/jira/browse/VELOCITY-491
Project: Velocity
Issue Type: Bug
Components: Build
Affects Versions: 1.4
Reporter: Vincent Massol
Priority: Blocker
Velocity dep should not repackage any external dependencies. At least it shouldn't do that while keeping the original package name as this leads to clashes with other libraries. For example the project I'm working on includes ORO 2.0.8 but as velocity-dep also includes ORO (but another version of it) it leads to weird errors depending on how the classpath/classloaders are used.
This project is using Maven2 to build. See http://jira.codehaus.org/browse/MEV-459 for the issue I've raised against Maven2 (but it's really a Velocity issue).
Thanks
-Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Closed: (VELOCITY-491) Velocity-dep repackages the Jakarta
ORO classes
Posted by "Henning Schmiedehausen (JIRA)" <de...@velocity.apache.org>.
[ https://issues.apache.org/jira/browse/VELOCITY-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henning Schmiedehausen closed VELOCITY-491.
-------------------------------------------
> Velocity-dep repackages the Jakarta ORO classes
> -----------------------------------------------
>
> Key: VELOCITY-491
> URL: https://issues.apache.org/jira/browse/VELOCITY-491
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4
> Reporter: Vincent Massol
> Priority: Blocker
>
> Velocity dep should not repackage any external dependencies. At least it shouldn't do that while keeping the original package name as this leads to clashes with other libraries. For example the project I'm working on includes ORO 2.0.8 but as velocity-dep also includes ORO (but another version of it) it leads to weird errors depending on how the classpath/classloaders are used.
> This project is using Maven2 to build. See http://jira.codehaus.org/browse/MEV-459 for the issue I've raised against Maven2 (but it's really a Velocity issue).
> Thanks
> -Vincent
--
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-491) Velocity-dep repackages the Jakarta
ORO classes
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/VELOCITY-491?page=all ]
Henning Schmiedehausen resolved VELOCITY-491.
---------------------------------------------
Resolution: Invalid
Works as intended. See my explanation above.
> Velocity-dep repackages the Jakarta ORO classes
> -----------------------------------------------
>
> Key: VELOCITY-491
> URL: http://issues.apache.org/jira/browse/VELOCITY-491
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4
> Reporter: Vincent Massol
> Priority: Blocker
>
> Velocity dep should not repackage any external dependencies. At least it shouldn't do that while keeping the original package name as this leads to clashes with other libraries. For example the project I'm working on includes ORO 2.0.8 but as velocity-dep also includes ORO (but another version of it) it leads to weird errors depending on how the classpath/classloaders are used.
> This project is using Maven2 to build. See http://jira.codehaus.org/browse/MEV-459 for the issue I've raised against Maven2 (but it's really a Velocity issue).
> Thanks
> -Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-491) Velocity-dep repackages the
Jakarta ORO classes
Posted by "Vincent Massol (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/VELOCITY-491?page=comments#action_12448965 ]
Vincent Massol commented on VELOCITY-491:
-----------------------------------------
Hi Henning,
I'm NOT using velocity-dep.jar. I'm only using the velocity-1.4.jar but its POM has a dependency on velocity-dep... I'll create another issue.
Thanks
-Vincent
> Velocity-dep repackages the Jakarta ORO classes
> -----------------------------------------------
>
> Key: VELOCITY-491
> URL: http://issues.apache.org/jira/browse/VELOCITY-491
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4
> Reporter: Vincent Massol
> Priority: Blocker
>
> Velocity dep should not repackage any external dependencies. At least it shouldn't do that while keeping the original package name as this leads to clashes with other libraries. For example the project I'm working on includes ORO 2.0.8 but as velocity-dep also includes ORO (but another version of it) it leads to weird errors depending on how the classpath/classloaders are used.
> This project is using Maven2 to build. See http://jira.codehaus.org/browse/MEV-459 for the issue I've raised against Maven2 (but it's really a Velocity issue).
> Thanks
> -Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
[jira] Commented: (VELOCITY-491) Velocity-dep repackages the
Jakarta ORO classes
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/VELOCITY-491?page=comments#action_12448960 ]
Henning Schmiedehausen commented on VELOCITY-491:
-------------------------------------------------
Please see http://svn.apache.org/repos/asf/jakarta/velocity/engine/trunk/WHY_TWO_JARS.txt
There is a distinct reason why we package the jars like that. That is why there is velocity.jar and velocity-dep.jar. velocity-dep.jar is *intended* to help users to get up to speed quickly without going through the "uh, I need *another* jar?" dependency hell. Once you come to the point where you have dependency clashes, you should already be seasoned enough to not use the -dep jar but the vanilla one and add your dependencies externally.
In a nutshell: If any project gets dependency clashes due to the velocity-dep jar, it is using the wrong jar and should use the vanilla "velocity.jar".
This is not going to change. velocity-dep is a tool for beginners. I agree that we must stress this more in our documentation.
> Velocity-dep repackages the Jakarta ORO classes
> -----------------------------------------------
>
> Key: VELOCITY-491
> URL: http://issues.apache.org/jira/browse/VELOCITY-491
> Project: Velocity
> Issue Type: Bug
> Components: Build
> Affects Versions: 1.4
> Reporter: Vincent Massol
> Priority: Blocker
>
> Velocity dep should not repackage any external dependencies. At least it shouldn't do that while keeping the original package name as this leads to clashes with other libraries. For example the project I'm working on includes ORO 2.0.8 but as velocity-dep also includes ORO (but another version of it) it leads to weird errors depending on how the classpath/classloaders are used.
> This project is using Maven2 to build. See http://jira.codehaus.org/browse/MEV-459 for the issue I've raised against Maven2 (but it's really a Velocity issue).
> Thanks
> -Vincent
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org