[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797189#action_12797189
]
stack commented on HBASE-1433:
------------------------------
(Redo of a mangled iphone comment of mine that I just deleted)
On having to be connected to the net, it should be the case that if the jar is
not in the local ivy cache, then the build should not go to the net. If this
is not the case, we should fix it. This should do away with having to set up
local repo. The only difficulty that I see will be not going to the net to
check for new SNAPSHOTs (Kay Kay says this above).
In deleted comment, I made the silly remark that build may not be more complex,
just different. Thinking on it, there'll be more moving parts and more to
learn, etc. as Andy says above.
For me, main reasons we're doing this change is to keep alignment the parent
project. Ivy also helps with maven publishing, another means of making hbase
available especially for folks embedding (we could write ant tasks ourselves to
do this but if we use ivy we can just rob the tested parent projects ant tasks
and bring them local).
> 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.
