[
https://issues.apache.org/jira/browse/HBASE-4327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095730#comment-13095730
]
Joep Rottinghuis commented on HBASE-4327:
-----------------------------------------
I'm happy to provide a patch. I see three options:
1) modify the POM to provide a separate property for the hadoop-annotation
dependency version. That way one can depend on hadoop-0.22-SNAPSHOT (or
whatever other 0.22 version) for hadoop-common, hadoop-hdfs, etc, and one could
grab hadoop-annotations from 0.23 or 0.24.
2) modify the POM to have an entirely separate 0.22 profile. Again the profile
would have to point to hadoop-annotation from a 0.23 or 0.24/trunk snapshot.
3) Not modify the pom, manually build hadoop-annotations from trunk with a
modified / faked 0.22 version and deploy to local repo. This would solve my own
internal problem, but is not likely to be a satisfying solution for uploading
to the apache repo's (not sure if any committer is willing to upload such
hadoop-annotation-0.22-SNAPSHOT.jar).
Any suggestions?
> Compile HBase against hadoop 0.22
> ---------------------------------
>
> Key: HBASE-4327
> URL: https://issues.apache.org/jira/browse/HBASE-4327
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 0.92.0
> Reporter: Joep Rottinghuis
> Fix For: 0.92.0
>
>
> Pom contains a profile for hadoop-0.20 and one for hadoop-0.23, but not one
> for hadoop-0.22.
> When overriding hadoop.version to 0.22, then the (compile-time) dependency on
> hadoop-annotations cannot be met.
> That exists on 0.23 and 0.24/trunk, but not on 0.22.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
