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

Scott Carey commented on AVRO-995:
----------------------------------

Additionally, I will not be able to commit this, or review or commit any other 
tickets in the next 11 days due to very limited Internet access.

I am +1 on this one as is.
                
> Java: Update Dependencies for 1.6.2
> -----------------------------------
>
>                 Key: AVRO-995
>                 URL: https://issues.apache.org/jira/browse/AVRO-995
>             Project: Avro
>          Issue Type: Improvement
>            Reporter: Scott Carey
>            Assignee: Scott Carey
>             Fix For: 1.6.2
>
>         Attachments: AVRO-995.patch
>
>
> A few of our dependencies need upgrading.  In particular, I have been hit by 
> a bug in Jackson that is fixed by the latest release 
> (http://jira.codehaus.org/browse/JACKSON-462).
> Summary:  I will submit a patch that updates everything to the next bugfix or 
> very minor release, other than paranamer, thrift, and hadoop.
> Details:
> (using maven versions plugin)
> On the dependency side:
> [INFO]   com.thoughtworks.paranamer:paranamer ................ 2.3 -> 
> 2.4-debug
>   could not find info about what is new in 2.4.  I do not think we should 
> upgrade until we have more info
> [INFO]   net.sf.jopt-simple:jopt-simple ............................ 4.1 -> 
> 4.3
>   minor extra features (http://pholser.github.com/jopt-simple/changes.html)
> [INFO]   org.apache.hadoop:hadoop-core .................... 0.20.205.0 -> 
> 1.0.0
>   renamed 0.20.205, no need to update yet.
> [INFO]   org.codehaus.jackson:jackson-mapper-asl ............... 1.8.6 -> 
> 1.9.3
>   I suggest we upgrade to 1.8.7.
> [INFO]   org.jboss.netty:netty ..................... 3.2.6.Final -> 
> 3.2.7.Final
>   bugfix release
> [INFO]   org.apache.thrift:libthrift ........................... 0.7.0 -> 
> 0.8.0
>   Is this a minor / bugfix release?  If so we should update, otherwise wait 
> until Avro 1.7.x
> [INFO]   org.slf4j:slf4j-api ................................... 1.6.3 -> 
> 1.6.4
> [INFO]   org.slf4j:slf4j-simple ................................ 1.6.3 -> 
> 1.6.4
>   Minor bugfixes (http://www.slf4j.org/news.html)
> On the plugin side: (mvn versions:display-plugin-updates)
> [INFO]   maven-antrun-plugin ...................................... 1.6 -> 
> 1.7 
>   minor, looks safe: 
> (http://mail-archives.apache.org/mod_mbox/maven-announce/201111.mbox/%3CCALhtWke1=w6nv2u85nkgqm0zxo3khyzdc8hazkhhvywjbuv...@mail.gmail.com%3E)
> [INFO]   maven-gpg-plugin ......................................... 1.3 -> 1.4
>   minor update 
> (http://mail-archives.apache.org/mod_mbox/maven-announce/201108.mbox/%3CCA+nPnMw_3zQQCpzybQvo-QZFMCogvH31WEhxQnZ=cdzgxsr...@mail.gmail.com%3E)
> [INFO]   maven-checkstyle-plugin .................................. 2.6 -> 2.8
>   we avoided 2.7 before for some reason: 
> (http://mail-archives.apache.org/mod_mbox/maven-dev/201108.mbox/%3ccapoybqsvu+kup5vuce8rc6mjb9rykr2cpig+rvbe5o8teo6...@mail.gmail.com%3E)
>   useful new feature: 
> (http://mail-archives.apache.org/mod_mbox/maven-announce/201111.mbox/%3C15365449.01320142181746.JavaMail.mark@MARK%3E)
> [INFO]   maven-surefire-plugin .................................. 2.10 -> 2.11
>   lots of bug fixes and long requested new features: 
> (http://mail-archives.apache.org/mod_mbox/maven-announce/201112.mbox/%3CCA+jQputH_uA2Ue6JqiHp1YeNo=qqxgcpdtgq9vv1aw_psqk...@mail.gmail.com%3E)
> [INFO]   maven-shade-plugin ....................................... 1.4 -> 1.5
>   minor looks  safe: 
> (http://mail-archives.apache.org/mod_mbox/maven-announce/201111.mbox/%3C1076639049.01320107865464.JavaMail.benson@tinfoilhat.local%3E)
> [INFO]   maven-archetype-plugin ................................... 2.1 -> 2.2
>   
> http://mail-archives.apache.org/mod_mbox/maven-announce/201111.mbox/%3CCALhtWkeLyc-tA2NCh3xYR06W+eGiWd46fS=R=ngjon14zrd...@mail.gmail.com%3E

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to