[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796849#action_12796849
]
Kay Kay commented on HBASE-1433:
--------------------------------
| One thing you aren't surfacing here is this change will require everyone who
wants to build HBase to have internet access on their build machines.
Nothing theoretically prevents from a build machine from hosting their own
internal ivy repository within the firewall and configuring ivysettings.xml
appropriately ( as another resolver ). But given the fact that hbase is using
no less than 3 snapshots of other open source projects ( + zookeeper , that
makes is four ) - I guess the need is to make sure that hbase does not fall
back too much from the code of the dependent projects and wait for the single
big merge. That will -vely affect the length of release cycles and the
confidence of milestone builds in the middle.
> 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.
