[ 
https://issues.apache.org/jira/browse/THRIFT-1956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13661741#comment-13661741
 ] 

Hudson commented on THRIFT-1956:
--------------------------------

Integrated in Thrift #646 (See [https://builds.apache.org/job/Thrift/646/])
    THRIFT-1956: Switch to Apache Commons Lang 3 (Revision 
0fd47dab1ba4bcb13c2a871ec4e0527c2c6c06bb)
THRIFT-1956: Switch to Apache Commons Lang 3 (Revision 
68f8bd77303e71cc9db63842a9d2fab18e87ec02)
THRIFT-1956: Switch to Apache Commons Lang 3 (Revision 
c28e04a1cb3254efec43e97bac5c9b226eb06f04)

     Result = SUCCESS
jfarrell : 
Files : 
* lib/java/build.xml
* lib/java/build.properties
* compiler/cpp/src/generate/t_java_generator.cc
* .gitignore
* 
lib/java/src/org/apache/thrift/transport/AutoExpandingBufferWriteTransport.java
* lib/java/src/org/apache/thrift/transport/AutoExpandingBufferReadTransport.java

jfarrell : 
Files : 
* debian/control

jfarrell : 
Files : 
* debian/control

                
> Switch to Apache Commons Lang 3
> -------------------------------
>
>                 Key: THRIFT-1956
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1956
>             Project: Thrift
>          Issue Type: Improvement
>            Reporter: Christoffer Sawicki
>            Assignee: Christoffer Sawicki
>            Priority: Minor
>             Fix For: 1.0
>
>         Attachments: Switch to Apache Commons Lang 3.diff
>
>
> Thrift for Java currently uses Apache Commons Lang 2.5.
> 3.0 was released in July of 2011 and provides lots of improvements.
> I have a project that uses Lang 3.x but Thrift drags in Lang 2.x. It would be 
> nice to get rid of the dependency on 2.x. (3.x is designed so that it can be 
> installed side by side with 2.x.)
> The downside of switching to Lang 3.x is that Thrift will no longer be 
> compatible with Java <= 4. I can't imagine this being a problem, but what do 
> you say?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to