[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797019#action_12797019
]
stack commented on HBASE-1433:
------------------------------
On having to be connected to the net, it shouldn't be too bad in that at least
with maven you could make it so it only went to the net if the wanted jar was
not present in the local cache (with snapshots iirc you could configure mvn to
only check for new ones every so often. We should do same for ivy or just so as
we do now and manage which hadoop snapshot we want) My guess is that can do
same for ivy
I am not sure the build gets more complex. It will be different for sure but
in alignment with our parent. I think the move to ivy will also open us up to
new vistas, new tools, etc For example, in maven there used to be a plugin to
generate eclipse files.
> 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.
