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

Sean Busbey commented on HBASE-16338:
-------------------------------------

repostatus of "branch" is before the patch is applied. a repostatus of "patch" 
would be after.

Maybe we could just always do our mvninstall at the root? Are we saving a 
significant amount of time by only doing per-module installs in the patch case?

> update jackson to 2.y
> ---------------------
>
>                 Key: HBASE-16338
>                 URL: https://issues.apache.org/jira/browse/HBASE-16338
>             Project: HBase
>          Issue Type: Task
>          Components: dependencies
>            Reporter: Sean Busbey
>            Assignee: Mike Drob
>             Fix For: 2.0.0-beta-2
>
>         Attachments: 16338.txt, HBASE-16338.v10.patch, HBASE-16338.v2.patch, 
> HBASE-16338.v3.patch, HBASE-16338.v5.patch, HBASE-16338.v6.patch, 
> HBASE-16338.v7.patch, HBASE-16338.v8.patch, HBASE-16338.v9.patch
>
>
> Our jackson dependency is from ~3 years ago. Update to the jackson 2.y line, 
> using 2.7.0+.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to