[ https://issues.apache.org/jira/browse/HBASE-7637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13560669#comment-13560669 ]
nkeywal commented on HBASE-7637: -------------------------------- It's possible to do this (cf. nomodules.patch) in the main pom.xml (on top of what you did). It has one advantage: you don't download (or need) the hadoop version you don'tuse. Without it, even if you build hbase for hadoop 1, you take hadoop 2 as well. > hbase-hadoop1-compat conflicts with -Dhadoop.profile=2.0 > -------------------------------------------------------- > > Key: HBASE-7637 > URL: https://issues.apache.org/jira/browse/HBASE-7637 > Project: HBase > Issue Type: Bug > Components: build > Affects Versions: 0.96.0 > Reporter: nkeywal > Assignee: Elliott Clark > Priority: Critical > Fix For: 0.96.0 > > Attachments: HBASE-7637-0.patch, nomodules.patch > > > I'm unclear on the root cause / fix. Here is the scenario: > {noformat} > mvn clean package install -Dhadoop.profile=2.0 -DskipTests > bin/start-hbase.sh > {noformat} > fails with > {noformat} > Caused by: java.lang.ClassNotFoundException: > org.apache.hadoop.metrics2.lib.MetricMutable > at java.net.URLClassLoader$1.run(URLClassLoader.java:202) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(URLClassLoader.java:190) > at java.lang.ClassLoader.loadClass(ClassLoader.java:306) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) > {noformat} > doing > {noformat} > rm -rf hbase-hadoop1-compat/target/ > {noformat} > makes it work. > In the pom.xml, we never reference hadoop2-compat. But doing so does not > help: hadoop1-compat is compiled and takes precedence over hadoop2... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira