[
https://issues.apache.org/jira/browse/HBASE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796891#action_12796891
]
Andrew Purtell commented on HBASE-1433:
---------------------------------------
I agree with Ryan. Why should I have to bother with setting up some kind of ivy
proxy (locally?) ? The first thing I do with Hadoop 0.21 is build to pull all
the dependencies into build/ivy/.... and then copy them by hand into a lib/
directory so I can put them on the Eclipse build path in a clean manner. Any
dependency changes, I have to fix them by hand. Before, SVN add/rm would handle
that for me -- the committer would deal with the dependency change. I'm not
looking forward to needing to do the same thing for HBase.
My interest here is not to discourage this if people are generally in favor,
but, personally, I prefer ant. I like make. I have a good relationship with
Eclipse but otherwise IDEs get in the way. Etc. I see no personal benefit for
using ivy or maven, just an (unnecessary, IMO) learning curve, additional work
if I need to fix something to get it to work for my changes, and a truckload of
external dependencies.
> 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.
