[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619483#comment-13619483
]
stack commented on HBASE-8224:
------------------------------
Thank you for sharing the pain [~enis].
Here is how I did snapshot upload to maven repo:
{code}
3547 svn revert -R .
3548 svn cleanup
3549 mvn clean org.codehaus.mojo:versions-maven-plugin:1.3.1:set
-DnewVersion=0.95.0-hadoop1-SNAPSHOT
3551 mvn -DskipTests install deploy
3552 svn revert -R .
3553 svn cleanup
3554 mvn clean org.codehaus.mojo:versions-maven-plugin:1.3.1:set
-DnewVersion=0.95.0-hadoop2-SNAPSHOT
3555 mvn -DskipTests -Dhadoop.profile=2.0 install deploy
{code}
It looks ok...
https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/hbase-client/
POMs don't explicitly reference a hadoop version though which is a little
disconcerting.
> 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
