[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796858#action_12796858
]
Kay Kay commented on HBASE-1433:
--------------------------------
| I just want to make it clear here that Ivy doesn't solve the problems you are
listing. Those problems existed before, and were solved before ivy. Ivy solves
your problem because you assume/need/depend on a complex dependency management
system. For those of us who don't care about ivy in fact lose something - a
easy to build hbase.
Ivy definitely is not a silver bullet to dependency management issues but it
makes a honest attempt towards that. I find the graph visualization / conflict
resolution very useful. Agree about hurting slow speed connection users - but
you can always set up a proxy dependency server pointing to a main repository
to handle it for you, to mitigate the issue.
> 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
> Fix For: 0.21.0
>
> Attachments: HBASE-1433.patch, HBASE-1433.patch, HBASE-1433.patch,
> HBASE-1433.patch
>
>
> We are almost close, except for the republication of artifacts to mapreduce
> snapshot repository from branch-0.21 (after applying the appropriate patch).
> It would be great to have this out for 0.21 .
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
