[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13618979#comment-13618979
]
stack commented on HBASE-8224:
------------------------------
Parent version must be hard-coded throughout
(http://jira.codehaus.org/browse/MNG-624).
The versions plugin rewrites the pom version in parent and in submodules for
you (have to use 1.3.1, the 2.0 is broke NPE'ing --
https://jira.codehaus.org/browse/MVERSIONS-201)
{code}
$ mvn clean org.codehaus.mojo:versions-maven-plugin:1.3.1:set
-DnewVersion=1.2.3-hadoop2-SNAPSHOT -Dhadoop.profile=2.0 install -DskipTests
assembly:single
{code}
So, unless someone has a better idea, I'm thinking that when we build to
publish, we use this ugly versions plugin to create jars w/ -hadoop1 suffix and
-hadoop2 suffix. I suppose will have to commit what the versions plugin writes
and then tag. Do it once for hadoop1 and once for hadoop2.
Let me try this for first 0.95RC
> 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
