there may be a better way but you can try making hadoop-3 profile default in your pom https://github.com/apache/hbase/blob/master/pom.xml#L2514-L2771 you can test and confirm but I believe the diff in the activation section is what controls which profile gets executed https://github.com/apache/hbase/blob/master/pom.xml#L2777-L2782
On Mon, Aug 13, 2018 at 8:33 AM Jean Charles Jabouille < jean-charles.jaboui...@kelkoogroup.com> wrote: > Hi, > > I'm working on a project which uses hbase 2.0 and hadoop 3.0. By default > Hbase dependencies are configured for hadoop 2.7.4. > > As I understand the switch to hadoop 3.0 can be done by doing something > like this: "mvn -Dhadoop.profile=3.0 clean package" on my project. This > works like a charm but I would like to integrate this property in my > pom.xml. I tried: > - to put this property in <properties> section of my pom.xml > - use properties-maven-plugin to inject the property dynamically > > When I launch mvn dependency:tree hadoop 2.7.4 is used. > > Someone can me on this subject please ? > > jc >
