hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Drob (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-16338) update jackson to 2.y
Date Tue, 17 Oct 2017 15:20:00 GMT

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

Mike Drob commented on HBASE-16338:

So... I think that the problems all relate to the {{\[WARNING] The POM for org.apache.hbase:hbase-client:jar:3.0.0-SNAPSHOT
is invalid, transitive dependencies (if any) will not be available, enable debug logging for
more details}} style messages. I suspect that the reason it thinks the poms are invalid is
because it is mixing and matching pre-patch and post-patch artifacts somewhere in the build,
with all the mvn install action that is going on. Can we clean the repository between running
the checks on master and the checks on patch? Something like {{find $M2_REPO -type d -name
'*-SNAPSHOT' -exec rm -rf {} \;}}?

> 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

View raw message