[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619269#comment-13619269
]
Enis Soztutar commented on HBASE-8224:
--------------------------------------
He was talking about the artifact name containing the hadoop1 or 2 suffix,
instead of the version. It is close to the one I was talking about above, where
we have two poms per module.
The module artifacts will be named hbase-client-hadoop1, and the version will
still be 0.95.0. So the final artifact name will be
hbase-client-hadoop1-0.95.0.jar.
We can supply an alternate file using mvn -f flag. But having the build is
already modular, we have to test it.
> 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
>
>
> 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
