[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733042#comment-13733042 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #656 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/656/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string; ADD MISSED FILE (stack: rev 1511444) * /hbase/trunk/dev-support/generate-hadoopX-poms.sh > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733007#comment-13733007 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in hbase-0.95-on-hadoop2 #223 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/223/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1511443) * /hbase/branches/0.95/dev-support/generate-hadoopX-poms.sh > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732898#comment-13732898 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in hbase-0.95 #413 (See [https://builds.apache.org/job/hbase-0.95/413/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1511443) * /hbase/branches/0.95/dev-support/generate-hadoopX-poms.sh > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732733#comment-13732733 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in HBase-TRUNK #4352 (See [https://builds.apache.org/job/HBase-TRUNK/4352/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string; ADD MISSED FILE (stack: rev 1511444) * /hbase/trunk/dev-support/generate-hadoopX-poms.sh > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732603#comment-13732603 ] stack commented on HBASE-8224: -- [~jmhsieh] Sorry about that. Fixed. Let me add release note too (doc is to follow when I exercise first release using this script). > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732291#comment-13732291 ] Sergey Shelukhin commented on HBASE-8224: - Do you guys want to populate release notes, so that the potential consumers of these who were not involved in the JIRA could understand what changed? Thanks > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13732069#comment-13732069 ] Jonathan Hsieh commented on HBASE-8224: --- Hey [~saint@gmail.com], the svn commit seems to be missing the dev-support scripts. Can you or someone who tested it commit the correct version? > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728337#comment-13728337 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in hbase-0.95-on-hadoop2 #215 (See [https://builds.apache.org/job/hbase-0.95-on-hadoop2/215/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1509811) * /hbase/branches/0.95/hbase-client/pom.xml * /hbase/branches/0.95/hbase-common/pom.xml * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java * /hbase/branches/0.95/hbase-examples/pom.xml * /hbase/branches/0.95/hbase-hadoop1-compat/pom.xml * /hbase/branches/0.95/hbase-hadoop2-compat/pom.xml * /hbase/branches/0.95/hbase-it/pom.xml * /hbase/branches/0.95/hbase-prefix-tree/pom.xml * /hbase/branches/0.95/hbase-server/pom.xml * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java * /hbase/branches/0.95/pom.xml > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728178#comment-13728178 ] Hudson commented on HBASE-8224: --- FAILURE: Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #649 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/649/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1509813) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-common/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java * /hbase/trunk/hbase-examples/pom.xml * /hbase/trunk/hbase-hadoop1-compat/pom.xml * /hbase/trunk/hbase-hadoop2-compat/pom.xml * /hbase/trunk/hbase-it/pom.xml * /hbase/trunk/hbase-prefix-tree/pom.xml * /hbase/trunk/hbase-server/pom.xml * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java * /hbase/trunk/pom.xml > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728182#comment-13728182 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in HBase-TRUNK #4334 (See [https://builds.apache.org/job/HBase-TRUNK/4334/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1509813) * /hbase/trunk/hbase-client/pom.xml * /hbase/trunk/hbase-common/pom.xml * /hbase/trunk/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java * /hbase/trunk/hbase-examples/pom.xml * /hbase/trunk/hbase-hadoop1-compat/pom.xml * /hbase/trunk/hbase-hadoop2-compat/pom.xml * /hbase/trunk/hbase-it/pom.xml * /hbase/trunk/hbase-prefix-tree/pom.xml * /hbase/trunk/hbase-server/pom.xml * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java * /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java * /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java * /hbase/trunk/pom.xml > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728157#comment-13728157 ] Hudson commented on HBASE-8224: --- SUCCESS: Integrated in hbase-0.95 #396 (See [https://builds.apache.org/job/hbase-0.95/396/]) HBASE-8224 Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string (stack: rev 1509811) * /hbase/branches/0.95/hbase-client/pom.xml * /hbase/branches/0.95/hbase-common/pom.xml * /hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/util/JVM.java * /hbase/branches/0.95/hbase-examples/pom.xml * /hbase/branches/0.95/hbase-hadoop1-compat/pom.xml * /hbase/branches/0.95/hbase-hadoop2-compat/pom.xml * /hbase/branches/0.95/hbase-it/pom.xml * /hbase/branches/0.95/hbase-prefix-tree/pom.xml * /hbase/branches/0.95/hbase-server/pom.xml * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/constraint/package-info.java * /hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/thrift/HThreadedSelectorServerArgs.java * /hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestMasterNoCluster.java * /hbase/branches/0.95/pom.xml > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727932#comment-13727932 ] Nick Dimiduk commented on HBASE-8224: - Green lights from me. I don't know the release plugin well enough to test that side out. Also, I saw your earlier comment about the other changes, so don't mind me. +1. > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727869#comment-13727869 ] Nick Dimiduk commented on HBASE-8224: - I'm giving this a spin too. Will let you know what I find. What's with sneaking in the unrelated formatting changes in the v5 patch? ;) > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727784#comment-13727784 ] Brock Noland commented on HBASE-8224: - [~saint@gmail.com] yes it does seem to be working! Thx!! > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727300#comment-13727300
]
Hadoop QA commented on HBASE-8224:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595528/8224v5.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6563//console
This message is automatically generated.
> 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727233#comment-13727233 ] stack commented on HBASE-8224: -- [~brocknoland] Do the SNAPSHOTs work for you boss? > 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, 8224v5.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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[
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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[
https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727018#comment-13727018
]
Hadoop QA commented on HBASE-8224:
--
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12595489/8224.gen.scriptv3.txt
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 3 new
or modified tests.
{color:green}+1 hadoop1.0{color}. The patch compiles against the hadoop
1.0 profile.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-protocol.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-client.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-examples.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-prefix-tree.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/6560//console
This message is automatically generated.
> 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
[jira] [Commented] (HBASE-8224) Publish hbase build against h1 and h2 adding '-hadoop1' or '-hadoop2' to version string
[ https://issues.apache.org/jira/browse/HBASE-8224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13726929#comment-13726929 ] stack commented on HBASE-8224: -- I tested building assemblies. They seem to work. Now let me try and use the mvn release plugin. See what it thinks. > 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
