[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617953#comment-13617953
]
Enis Soztutar commented on HBASE-8224:
--------------------------------------
In one of the comments here:
http://maven.40175.n5.nabble.com/How-to-deploy-with-classifier-td5523009.html ,
they basically say that one module should correspond to one artifact, and a
bunch of discussions around the jdk14, jdk15 classifiers.
How about creating one empty module per hbase module, and put the hadoop2 poms
there.
{code}
hbase-client
hbase-hadoop-2-support/hbase-client-hadoop2
hbase-server
hbase-hadoop-2-support/hbase-server-hadoop2
....
{code}
Then we do not even have to change the version, or have a profile for Hadoop2.
All will be build. Wdyt boss. Overkill?
> 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
