[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796042#action_12796042
]
stack commented on HBASE-1433:
------------------------------
.bq I have not. That is tricky because it pulls the latest snapshot across
three different projects ( core . hdfs, mapreduce ) . Also - one of the hdfs
snapshots (0.21 ) seemed to pull (0.22) from core. We also need to have some
sort of conflict resolver specific to core / hdfs / mapreduce to prevent
similar conflicts ( as opposed to the default one ).
A custom conflict resolver sounds like loads of fun (smile). If a 0.21 hdfs
snapshot is pulling in 0.22, that sounds well broke.
How about putting up a patch that leaves the hadoop stuff as checkins and not
pull these from a repo just yet (or, maybe if you just check in commons, and
pull the other two, does that help)? I suggest this because the patch as is
where it moves the bulk of the jar includes to instead be ivy pulls is a nice
fat contribution. It also gets you what you need, an updated lucene?
Good stuff on the fact that jsp-2.1 is being pulled already and jersery-json is
a transitive include.
> Update hbase build to match core, use ivy, publish jars to maven repo, etc.
> ---------------------------------------------------------------------------
>
> Key: HBASE-1433
> URL: https://issues.apache.org/jira/browse/HBASE-1433
> Project: Hadoop HBase
> Issue Type: Task
> Affects Versions: 0.20.2
> Reporter: stack
> Attachments: HBASE-1433.patch
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
