As of 0.96 hbase has become a multi-module project. The artifact to which you're referring is now the parent pom. You'll need to update your projects to consume the new structure, and perhaps the new APIs as well.
There's also work on adding maven archetypes in progress. I believe we have a mapreduce application archtype as part of that effort. This will hopefully make things easier. Have a look at our book for changes that are relevant to you, http://hbase.apache.org. -n On Wed, May 4, 2016 at 1:06 PM, Jan David Schneider < [email protected]> wrote: > Dear Developers, > > I am very sorry, if I am contacting the wrong email-list to adress my > issue. Nevertheless I want to ask you about the following: When importing > different versions of Hbase (specifically all versions >0.94.27) through > the dependencies of my Maven project in IntelliJ, the dependency cannot be > resolved, because IntelliJ cannot find the corresponding jar in the Apache > Maven repo. I'm talking about the following dependency: > <dependency> > <groupId>org.apache.hbase</groupId> > <artifactId>hbase</artifactId> > <version>1.2.1</version> > <dependency> > > Soon after I found out that the link (which IntelliJ tries to resolve) to > the > repo.maven.apache.org/maven2/org/apache/hbase/hbase/1.2.1/hbase-1.2.1.jar > aswell as the coressponding links to the Hbase jars with a version newer > than 0.94.27 lead to an Error 404. > Am I (or is IntelliJ) doing something wrong? > > If that is not the case: Could you make the Hbase jars available again in > the Apache Maven repo? Being able to use a newer version of the Hbase jar > would help me very much, since my cluster displays a > java.lang.NoClassDefFoundError: org/apache/hadoop/hbase/HBaseConfiguration > Error everytime I execute a MapReduce Job and I suspect the missing (or > too old of a version) Hbase jar to be the reason, since I'm importing the > HBaseConfiguration Class via > import org.apache.hadoop.hbase.HBaseConfiguration. > > Thank you for your help and again my apologies, if I am adressing the > wrong email addresses. > > Best Regards, > Jan > > > > >
