[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13685923#comment-13685923
]
Brock Noland commented on HBASE-8224:
-------------------------------------
I have a pom which depends on the hadoop2 client jar:
{noformat}
<dependency>
<groupId>org.apache.hbase</groupId>
<artifactId>hbase-client</artifactId>
<version>0.95.1-hadoop2-SNAPSHOT</version>
</dependency>
{noformat}
and it works fine if I specify -Dhadoop.profile=2.0
{noformat}
[brock@bigboy hbase-client-hadoop2-example]$ mvn dependency:tree
-Dhadoop.profile=2.0
...
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
hbase-client-hadoop2-example ---
[INFO] org.apache.hbase:hbase-client-hadoop2-example:jar:1.0
[INFO] \- org.apache.hbase:hbase-client:jar:0.95.1-hadoop2-SNAPSHOT:compile
...
[INFO] +- org.apache.hadoop:hadoop-client:jar:2.0.2-alpha:compile
{noformat}
However if hadoop.profile is left off, then it pulls in 1.X. Should make
hadoop.profile required?
> Add '-hadoop1' or '-hadoop2' to our version string
> --------------------------------------------------
>
> Key: HBASE-8224
> URL: https://issues.apache.org/jira/browse/HBASE-8224
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Attachments: 8224-adding.classifiers.txt, hbase-8224-proto1.patch
>
>
> So we can publish both the hadoop1 and the hadoop2 jars to a maven
> repository, and so we can publish two packages, one for hadoop1 and one for
> hadoop2, given how maven works, our only alternative (to the best of my
> knowledge and after consulting others) is by amending the version string to
> include hadoop1 or 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
