[jira] Commented: (MEV-459) Velocity-dep includes Apache ORO thus clashing with ORO dependency
[ http://jira.codehaus.org/browse/MEV-459?page=comments#action_79884 ] Vincent Massol commented on MEV-459: Raised against Velocity at https://issues.apache.org/jira/browse/VELOCITY-491 Velocity-dep includes Apache ORO thus clashing with ORO dependency -- Key: MEV-459 URL: http://jira.codehaus.org/browse/MEV-459 Project: Maven Evangelism Issue Type: Bug Components: Dependencies Reporter: Vincent Massol If a project is using ORO in version 2.0.8 then velocity-dep clashes with it as it includes ORO with the original package name (a really really bad practice). For information, the problem arises for example with Perl5Substitution.appendSubstitution(java.lang.StringBuffer stringBuffer, org.apache.oro.text.regex.MatchResult matchResult, int i, java.lang.String string, org.apache.oro.text.regex.PatternMatcher patternMatcher, org.apache.oro.text.regex.Pattern pattern) which is valid in ORO 2.0.8 but not in the version inside velocity-dep. This problem should be raised against the Velocity project as it should not be allowed to internally include another external package. -- 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
[jira] Commented: (MEV-459) Velocity-dep includes Apache ORO thus clashing with ORO dependency
[ http://jira.codehaus.org/browse/MEV-459?page=comments#action_79885 ] Henning Schmiedehausen commented on MEV-459: Please remove velocity-dep jar from your dependencies and add velocity.jar. Add its dependencies (commons-lang, commons-collections, oro) to your application. Velocity-dep includes Apache ORO thus clashing with ORO dependency -- Key: MEV-459 URL: http://jira.codehaus.org/browse/MEV-459 Project: Maven Evangelism Issue Type: Bug Components: Dependencies Reporter: Vincent Massol If a project is using ORO in version 2.0.8 then velocity-dep clashes with it as it includes ORO with the original package name (a really really bad practice). For information, the problem arises for example with Perl5Substitution.appendSubstitution(java.lang.StringBuffer stringBuffer, org.apache.oro.text.regex.MatchResult matchResult, int i, java.lang.String string, org.apache.oro.text.regex.PatternMatcher patternMatcher, org.apache.oro.text.regex.Pattern pattern) which is valid in ORO 2.0.8 but not in the version inside velocity-dep. This problem should be raised against the Velocity project as it should not be allowed to internally include another external package. -- 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
[jira] Commented: (MEV-459) Velocity-dep includes Apache ORO thus clashing with ORO dependency
[ http://jira.codehaus.org/browse/MEV-459?page=comments#action_79887 ] Vincent Massol commented on MEV-459: Henning, I don't have verlocity-dep.jar in my dependencies!!! It's added transitively by the velocity-1.4.jar Thanks -Vincent Velocity-dep includes Apache ORO thus clashing with ORO dependency -- Key: MEV-459 URL: http://jira.codehaus.org/browse/MEV-459 Project: Maven Evangelism Issue Type: Bug Components: Dependencies Reporter: Vincent Massol If a project is using ORO in version 2.0.8 then velocity-dep clashes with it as it includes ORO with the original package name (a really really bad practice). For information, the problem arises for example with Perl5Substitution.appendSubstitution(java.lang.StringBuffer stringBuffer, org.apache.oro.text.regex.MatchResult matchResult, int i, java.lang.String string, org.apache.oro.text.regex.PatternMatcher patternMatcher, org.apache.oro.text.regex.Pattern pattern) which is valid in ORO 2.0.8 but not in the version inside velocity-dep. This problem should be raised against the Velocity project as it should not be allowed to internally include another external package. -- 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
