You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Vincent Massol (JIRA)" <ji...@codehaus.org> on 2006/11/11 11:53:32 UTC

[jira] Created: (MEV-459) Velocity-dep includes Apache ORO thus clashing with ORO dependency

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 should not depend on Velocity-dep

Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90043 ] 

Carlos Sanchez commented on MEV-459:
------------------------------------

Velocity 1.5 is out, check this pom to see if everything looks right 
http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/poms/velocity-1.5.pom.carlos

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Henri Yandell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_80346 ] 
            
Henri Yandell commented on MEV-459:
-----------------------------------

This seems like a problem then. People will be unable to use Velocity 1.4 as it has a screwed up pom, and the Velocity guys aren't going to be creating a release just to fix a Maven screw-up.

Velocity 1.5 is on its way, so if someone uses the pom that is in Velocity's trunk when they add it to the maven repo then that one will be fine (odd that the 1.4 pom is bad, as there has been a pom in velocity since 2002 and I can't see it ever having this -deps dependency).

Additionallyl, should the velocity-deps jar be in the maven repo at all? It seems like it should be removed as it's not intended for maven style use.

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Henri Yandell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_81917 ] 
            
Henri Yandell commented on MEV-459:
-----------------------------------

They've a 1.5 in the works, but I don't think there are any plans for a 1.4.1. It'd be a bit odd for them to release a 1.4.1 - "re-releasing 1.4 as 1.4.1 so the Maven repository can have a new pom".

So I think a 1.4-1 would be suitable here. Or we just leave it as a known problem and tell people to exclude the dependency.

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_80277 ] 
            
Carlos Sanchez commented on MEV-459:
------------------------------------

poms are not changed in repo or everything depending on them will break

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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

Posted by "Henning Schmiedehausen (JIRA)" <ji...@codehaus.org>.
    [ 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

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ 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

        

[jira] Commented: (MEV-459) Velocity should not depend on Velocity-dep

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_79899 ] 
            
Vincent Massol commented on MEV-459:
------------------------------------

Thanks Carlos. That's what I've done. I'm just raising it here to improve the POMs. I've also raised another issue on the Velocity project: http://issues.apache.org/jira/browse/VELOCITY-492

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90051 ] 

Vincent Massol commented on MEV-459:
------------------------------------

Hi Carlos,

This new POM looks good.

Thanks
-Vincent

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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] Closed: (MEV-459) Velocity should not depend on Velocity-dep

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEV-459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vincent Massol closed MEV-459.
------------------------------

    Resolution: Fixed

Fixed (not sure whom to assign to this)

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_80365 ] 
            
Carlos Sanchez commented on MEV-459:
------------------------------------

Well, they could be kind enough to make a 1.4.1 or something to help their maven users or we can do a 1.4-1 release as I did with groovy http://repo1.maven.org/maven2/groovy/groovy/1.0-jsr-05-1/ to fix a really really messed up pom.

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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 should not depend on Velocity-dep

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90052 ] 

Vincent Massol commented on MEV-459:
------------------------------------

I'm trying it on a real project right now and I'll close the issue if it works

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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] Updated: (MEV-459) Velocity should not depend on Velocity-dep

Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MEV-459?page=all ]

Carlos Sanchez updated MEV-459:
-------------------------------

    Summary: Velocity should not depend on Velocity-dep  (was: Velocity-dep includes Apache ORO thus clashing with ORO dependency)

So the problm is that Velocity should not depend on Velocity-dep and add all the dependencies in velocity.
You'd need to explicitly exclude velocity-dep until the velocity guys release a new version with the right pom.

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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

Posted by "Vincent Massol (JIRA)" <ji...@codehaus.org>.
    [ 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 should not depend on Velocity-dep

Posted by "Henri Yandell (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MEV-459?page=comments#action_80147 ] 
            
Henri Yandell commented on MEV-459:
-----------------------------------

If this was a pom badly generated by the Maven team (or someone other than the Velocity committers); shouldn't the existing pom get fixed?

> Velocity should not depend on Velocity-dep
> ------------------------------------------
>
>                 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