Another issue is that it pulls in many more libs as part of the dependency resolving process. This reminds me bit of
aptitude
and when you try to install Java, for example on Debian. It often wants to pull in a litany of "required" packages but upon closer look many are only recommended and need not to be installed.Finally you need to get the jar files somehow into your development environment. I am using Eclipse 3.5 on my Windows 7 PC as well as on my MacOS machines. If you have not run
ant
from the command line yet you have no jars downloaded and opening the project in Eclipse yields an endless amount of errors. You have two choices, you can run ant
and get all jars and then add them to the project in Eclipse. But that is rather static and does not work well with future changes. It also is not the "ivy" way to resolve the libraries automatically.![](https://cdn.statically.io/img/2.bp.blogspot.com/_Cib_A77V54U/S2xMXVWKaxI/AAAAAAAAAGA/11gv-69kUD4/s200/ivy-edit-libs.png)
A few more steps have to be done to get HBase working now - as in compiling without errors. The crucial one is editing the Ivy library and setting the HBase specific Ivy files. In particular the "Ivy settings path" and the properties file. The latter especially is specifying all the various version numbers that the ivy.xml is using. Without it the Ivy resolve process will fail with many errors all over the place. Please note that in the screen shot I added you see how it looks like on my Windows PC. The paths will be slightly different for your setup and probably even using another format if you are on a Mac or Linux machine. As long as you specify both you should be fine.
![](https://cdn.statically.io/img/4.bp.blogspot.com/_Cib_A77V54U/S2xMUo_zXbI/AAAAAAAAAF4/UKgdgVW-2Lg/s200/ivy-build-path.png)
As a temporary step you have to add two more static libraries that are in the
$HBASE_HOME/lib
directory: libthrift-0.2.0.jar
and zookeeper-3.2.2.jar
. Those will eventually be published on the Ivy repositories and then this step is obsolete (see INFRA-2461).Eventually you end up with three containers as shown in the second and third screen shot. The Eclipse toolbar now also has an Ivy "Resolve All Dependencies" button which you can use to trigger the download process. Personally I had to do this a few times as the mirrors with the jars seem to be flaky at times. I ended up with for example "hadoop-mapred.jar" missing. Another resolve run fixed the problem.
![](https://cdn.statically.io/img/4.bp.blogspot.com/_Cib_A77V54U/S2x4bMfpQMI/AAAAAAAAAGQ/-7XucgUd8kU/s200/ivy-eclipse.png)
Eclipse automatically compiles the project and if everything worked out it does so now without a hitch. Good luck!
Update: Added info about the yet still static thrift and zookeeper jars. See Kay Kay's comment below.