[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727151#comment-13727151
]
stack commented on HBASE-8224:
------------------------------
Played w/ maven release plugin. Updating my patch (I have to set into the pom,
the name of the pom itself!!!!! for the release plugin). Basically works.
Making a release, I'll operate on a copy of the release branch. I'll need to
replace the pom.xml w/ the pom.xml.hadoop1 or pom.xml.hadoop2 and check them
into the tag (else release plugin's checkin of the updated release version on
the end of the release:prepare fails -- we'll see). Here are commands I used
doing clean, prepare, and perform. Will add the below to updated doc in
refguide.
{code}
2246 ~/bin/mvn/bin/mvn -f pom.xml.hadoop2 release:clean
-Dproject.scm.developerConnection="scm:svn:https://svn.apache.org/repos/asf/hbase/branches/testing_remove";
-DtagBase="https://svn.apache.org/repos/asf/hbase/tags";
-DreleaseVersion=0.95.2-hadoop2 -DremoteTagging=false
-DsuppressCommitBeforeTag=true -DautoVersionSubmodules=true
2251 ~/bin/mvn/bin/mvn -f pom.xml.hadoop2 release:prepare
-Dproject.scm.developerConnection="scm:svn:https://svn.apache.org/repos/asf/hbase/branches/testing_remove";
-DtagBase="https://svn.apache.org/repos/asf/hbase/tags";
-DreleaseVersion=0.95.2-hadoop2 -DremoteTagging=false
-DsuppressCommitBeforeTag=true -DautoVersionSubmodules=true
-DcheckModificationExcludeList="**pom.xml.*"
2252 ~/bin/mvn/bin/mvn -f pom.xml.hadoop2 release:perform
-Dproject.scm.developerConnection="scm:svn:https://svn.apache.org/repos/asf/hbase/branches/testing_remove";
-DtagBase="https://svn.apache.org/repos/asf/hbase/tags";
-DreleaseVersion=0.95.2-hadoop2 -DremoteTagging=false
-DsuppressCommitBeforeTag=true -DautoVersionSubmodules=true
-DcheckModificationExcludeList="**pom.xml.*"
{code}
Some of the above config is redundant. TBD.
I'd like to check in what I have so far.
> Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to
> version string
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-8224
> URL: https://issues.apache.org/jira/browse/HBASE-8224
> Project: HBase
> Issue Type: Task
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 0.98.0, 0.95.2
>
> Attachments: 8224-adding.classifiers.txt, 8224.gen.script.txt,
> 8224.gen.scriptv3.txt, 8224.gen.scriptv3.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
