HBase
  1. HBase
  2. HBASE-1933

Upload Hbase jars to a public maven repository

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Blocker Blocker
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.90.0
    • Component/s: None
    • Labels:
      None

      Description

      There are many cool release of hadoop hbase and this project is an apache project, as the maven project.

      But the released jars must be download manually and then deploy to a private repository before they can be used by developer using maven2.

      Please could you upload the hbase jars on the public maven2 repository ?

      Of course, we can help to deploy those artifact if necessary.

        Issue Links

          Activity

          Cyril Lakech created issue -
          Hide
          stack added a comment -

          Can you write the pom and counsel on where we should put them when we release? Thanks.

          Show
          stack added a comment - Can you write the pom and counsel on where we should put them when we release? Thanks.
          Hide
          Cyril Lakech added a comment -

          Yes of course

          Here is a sample pom.xml for hbase 0.20.0

          <?xml version="1.0" encoding="UTF-8"?>
          <project>
          <modelVersion>4.0.0</modelVersion>
          <groupId>org.apache.hadoop</groupId>
          <artifactId>hbase</artifactId>
          <version>0.20.0</version>
          </project>

          When you release hbase you could upload the jar and this pom to the public maven repository. For instance, the hadoop avro project seems to be uploaded on the public repo. You could contact the hadoop avro team to know how do they upload their last release (avro 1.2.0)

          Show
          Cyril Lakech added a comment - Yes of course Here is a sample pom.xml for hbase 0.20.0 <?xml version="1.0" encoding="UTF-8"?> <project> <modelVersion>4.0.0</modelVersion> <groupId>org.apache.hadoop</groupId> <artifactId>hbase</artifactId> <version>0.20.0</version> </project> When you release hbase you could upload the jar and this pom to the public maven repository. For instance, the hadoop avro project seems to be uploaded on the public repo. You could contact the hadoop avro team to know how do they upload their last release (avro 1.2.0)
          Hide
          Cyril Lakech added a comment -

          How to upload a jar to the Apache directory ?

          The public answer :
          http://maven.apache.org/guides/mini/guide-central-repository-upload.html

          The apache internal answer :
          http://www.apache.org/dev/repository-faq.html

          Show
          Cyril Lakech added a comment - How to upload a jar to the Apache directory ? The public answer : http://maven.apache.org/guides/mini/guide-central-repository-upload.html The apache internal answer : http://www.apache.org/dev/repository-faq.html
          Hide
          Cyril Lakech added a comment -

          Here is a better pom, but you have to add the dependencies tag too:

          <project>
          <modelVersion>4.0.0</modelVersion>
          <groupId>org.apache.hadoop</groupId>
          <artifactId>hbase</artifactId>
          <packaging>jar</packaging>
          <name>Hadoop - HBase</name>
          <version>0.20.0</version>
          <description>HBase is the Hadoop database</description>
          <url>http://hadoop.apache.org/hbase</url>
          <licenses>
          <license>
          <name>The Apache Software License, Version 2.0</name>
          <url>http://www.apache.org/licenses/LICENSE-2.0.txt</url>
          <distribution>repo</distribution>
          </license>
          </licenses>
          <scm>
          <url>http://svn.apache.org/viewcvs.cgi/hadoop/hbase</url>
          </scm>
          </project>

          Do you plan to migrate from ant to maven ?

          Show
          Cyril Lakech added a comment - Here is a better pom, but you have to add the dependencies tag too: <project> <modelVersion>4.0.0</modelVersion> <groupId>org.apache.hadoop</groupId> <artifactId>hbase</artifactId> <packaging>jar</packaging> <name>Hadoop - HBase</name> <version>0.20.0</version> <description>HBase is the Hadoop database</description> <url> http://hadoop.apache.org/hbase </url> <licenses> <license> <name>The Apache Software License, Version 2.0</name> <url> http://www.apache.org/licenses/LICENSE-2.0.txt </url> <distribution>repo</distribution> </license> </licenses> <scm> <url> http://svn.apache.org/viewcvs.cgi/hadoop/hbase </url> </scm> </project> Do you plan to migrate from ant to maven ?
          Hide
          ryan rawson added a comment -

          There are no plans to migrate to maven, it doesn't generally solve any problem we are having and is complex. If you can create a patch that would add the appropriate ant task to upload to a maven repository, that would be great! Thanks!

          Show
          ryan rawson added a comment - There are no plans to migrate to maven, it doesn't generally solve any problem we are having and is complex. If you can create a patch that would add the appropriate ant task to upload to a maven repository, that would be great! Thanks!
          Hide
          Andrew Purtell added a comment -

          +1 on closing this issue as invalid.

          Show
          Andrew Purtell added a comment - +1 on closing this issue as invalid.
          Hide
          Cyril Lakech added a comment -

          I could help to upload your release to central maven repository.

          I could provide a repository (on googlecode for sample) with the hadoop project and then ask for a sync from the central repo and this repo.

          Andrew: If this issue is invalid, feel free to explain here why. thanks.

          Show
          Cyril Lakech added a comment - I could help to upload your release to central maven repository. I could provide a repository (on googlecode for sample) with the hadoop project and then ask for a sync from the central repo and this repo. Andrew: If this issue is invalid, feel free to explain here why. thanks.
          Hide
          steve_l added a comment -

          You can upload artifacts to the m2 repository without using Maven -indeed, Ivy happily pulls them down for your ant builds.

          Accordingly, I don' t think Invalid is the right way to close this bugrep.

          What is important is that the ASF don't let any apache release artifacts depend on any snapshot releases of other apache artifacts, so its only recently (Hadoop 0.21+) that its been possible, with HADOOP-3305. Without a copy of hadoop JARS, there's been little gain from having HBase in there.

          Accordingly I would recommend re-opening and marking as dependent on HADOOP-3302.

          Show
          steve_l added a comment - You can upload artifacts to the m2 repository without using Maven -indeed, Ivy happily pulls them down for your ant builds. Accordingly, I don' t think Invalid is the right way to close this bugrep. What is important is that the ASF don't let any apache release artifacts depend on any snapshot releases of other apache artifacts, so its only recently (Hadoop 0.21+) that its been possible, with HADOOP-3305 . Without a copy of hadoop JARS, there's been little gain from having HBase in there. Accordingly I would recommend re-opening and marking as dependent on HADOOP-3302 .
          Hide
          Andrew Purtell added a comment -

          Sorry, my misunderstanding. The tail of this issue looked like a request to switch the build system from ant to maven.

          Show
          Andrew Purtell added a comment - Sorry, my misunderstanding. The tail of this issue looked like a request to switch the build system from ant to maven.
          Hide
          stack added a comment -

          This relates to http://jira.codehaus.org/browse/MAVENUPLOAD-2642 (and HADOOP-3302). From Steve:

          "Historically it's not been possible to upload anything because Hadoop
          core depended on an unreleased snapshot of commons-cli, but as it's
          been rolled back to one that has shipped, it should be possible to
          resolve everything. All we need for HBase is to put together a POM
          with the core dependencies and then put up the artifacts that run
          against the not-quite-released Hadoop 0.21 version, which will be the
          first one with fully resolvable dependencies."

          Show
          stack added a comment - This relates to http://jira.codehaus.org/browse/MAVENUPLOAD-2642 (and HADOOP-3302 ). From Steve: "Historically it's not been possible to upload anything because Hadoop core depended on an unreleased snapshot of commons-cli, but as it's been rolled back to one that has shipped, it should be possible to resolve everything. All we need for HBase is to put together a POM with the core dependencies and then put up the artifacts that run against the not-quite-released Hadoop 0.21 version, which will be the first one with fully resolvable dependencies."
          Hide
          Brian Fox added a comment -

          Preferably you would use the repository.apache.org system to get the artifacts synced to central, since they are, well apache artifacts

          Show
          Brian Fox added a comment - Preferably you would use the repository.apache.org system to get the artifacts synced to central, since they are, well apache artifacts
          Hide
          stack added a comment -

          @Brian Thanks.

          Show
          stack added a comment - @Brian Thanks.
          Hide
          stack added a comment -

          Hadoop is pushing jars to apache repository on successful build. In hadoop build.xml I see a mvn-deploy target that http puts jars to the apache snapshot repo.

          Show
          stack added a comment - Hadoop is pushing jars to apache repository on successful build. In hadoop build.xml I see a mvn-deploy target that http puts jars to the apache snapshot repo.
          Hide
          stack added a comment -

          Pulling into 0.21 and assigning myself.

          Show
          stack added a comment - Pulling into 0.21 and assigning myself.
          stack made changes -
          Field Original Value New Value
          Assignee stack [ stack ]
          Fix Version/s 0.21.0 [ 12313607 ]
          Hide
          Karthik K added a comment -

          Would not this sort of depend on HBASE-1433 to complete the chain. Also - given that thrift and zookeeper do not have a maven repository yet - this might be tricky ?

          Show
          Karthik K added a comment - Would not this sort of depend on HBASE-1433 to complete the chain. Also - given that thrift and zookeeper do not have a maven repository yet - this might be tricky ?
          Hide
          Karthik K added a comment -

          This would be very useful for third-party integration . +1 on the idea. Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects ( that makes debugging / retrieving source / installation a nightmare ).

          Show
          Karthik K added a comment - This would be very useful for third-party integration . +1 on the idea. Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects ( that makes debugging / retrieving source / installation a nightmare ).
          Hide
          stack added a comment -

          .bq Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects

          How would you suggest w/ specify the dependency in the pom then?

          Show
          stack added a comment - .bq Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects How would you suggest w/ specify the dependency in the pom then?
          Hide
          Karthik K added a comment -

          .bq Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects

          How would you suggest w/ specify the dependency in the pom then?

          I meant - "preferably have releases of hbase dependent on releases of other dependent projects " , so that it easy to keep track of the corresponding source code + bugs if any.

          Show
          Karthik K added a comment - .bq Please make sure that the releases of hbase do not depend on the snapshots of other dependent projects How would you suggest w/ specify the dependency in the pom then? I meant - "preferably have releases of hbase dependent on releases of other dependent projects " , so that it easy to keep track of the corresponding source code + bugs if any.
          Karthik K made changes -
          Link This issue relates to THRIFT-363 [ THRIFT-363 ]
          Karthik K made changes -
          Link This issue relates to ZOOKEEPER-224 [ ZOOKEEPER-224 ]
          Hide
          Karthik K added a comment -

          This issue kind of , depends on the maven artifacts of the other 2 projects (thrift / zookeeper) . So people interested in this - can vote / contribute to the other ones. Zookeeper is going to be available eventually soon (3.3.0). Thrift needs help though.

          Assuming that is the case - we should be all set for the publishing of .pom / ivy.xml for hbase .

          Show
          Karthik K added a comment - This issue kind of , depends on the maven artifacts of the other 2 projects (thrift / zookeeper) . So people interested in this - can vote / contribute to the other ones. Zookeeper is going to be available eventually soon (3.3.0). Thrift needs help though. Assuming that is the case - we should be all set for the publishing of .pom / ivy.xml for hbase .
          Karthik K made changes -
          Link This issue relates to HBASE-1433 [ HBASE-1433 ]
          Hide
          stack added a comment -

          I haven't checked yet but maybe we can push our thrift and zk to maven ourselves to the apache maven repo. We can ask the respective projects if its ok w/ them but we could do a manual put w/ a coarse pom?

          Show
          stack added a comment - I haven't checked yet but maybe we can push our thrift and zk to maven ourselves to the apache maven repo. We can ask the respective projects if its ok w/ them but we could do a manual put w/ a coarse pom?
          Hide
          Karthik K added a comment -
          I haven't checked yet but maybe we can push our thrift and zk to maven ourselves to the apache maven repo. We can ask the respective projects if its ok w/ them but we could do a manual put w/ a coarse pom?

          As long as the project maintainers are ok with the same - that should work. Caveats:

          • If we are going to push it ourselves - then the snapshot release becomes kind of orphaned. With zk - I foresee less issues since they already have their maven integration in place and it is just a question of them integrating with their build process to publish to apache snapshot repository ( like - core, hdfs, mapreduce etc. ).
          • Thrift is tricky because there is no build process available yet. Even if we push the latest code to snapshot (we can't retroactively push version to maven repository , I guess) , that would mean that we need to look back into hbase about upgrading thrift dependency. It is definitely doable but just to be aware, though.
          Show
          Karthik K added a comment - I haven't checked yet but maybe we can push our thrift and zk to maven ourselves to the apache maven repo. We can ask the respective projects if its ok w/ them but we could do a manual put w/ a coarse pom? As long as the project maintainers are ok with the same - that should work. Caveats: If we are going to push it ourselves - then the snapshot release becomes kind of orphaned. With zk - I foresee less issues since they already have their maven integration in place and it is just a question of them integrating with their build process to publish to apache snapshot repository ( like - core, hdfs, mapreduce etc. ). Thrift is tricky because there is no build process available yet. Even if we push the latest code to snapshot (we can't retroactively push version to maven repository , I guess) , that would mean that we need to look back into hbase about upgrading thrift dependency. It is definitely doable but just to be aware, though.
          Hide
          Karthik K added a comment -

          THRIFT-363 is coming along pretty and should be close to getting published soon. That would leave the dependency on zk only and then we should be ready to publish hbase nightly snapshots from build.

          Show
          Karthik K added a comment - THRIFT-363 is coming along pretty and should be close to getting published soon. That would leave the dependency on zk only and then we should be ready to publish hbase nightly snapshots from build.
          Hide
          stack added a comment -

          The zk lads are talking about zk published to maven as part of the zk 3.3.0 release. It survived the edit of issues prepping for 3.3.0. Here is their issue on the matter: https://issues.apache.org/jira/browse/ZOOKEEPER-224.

          Show
          stack added a comment - The zk lads are talking about zk published to maven as part of the zk 3.3.0 release. It survived the edit of issues prepping for 3.3.0. Here is their issue on the matter: https://issues.apache.org/jira/browse/ZOOKEEPER-224 .
          stack made changes -
          Link This issue is blocked by INFRA-2461 [ INFRA-2461 ]
          Hide
          Karthik K added a comment -

          As mentioned in person -THRIFT-363 actually publishes mvn artifacts that can be used with both mvn and ivy. So for now - we can help check to publish mvn repository to a location of our choice and see if we would be able to integrate with thrift.

          Show
          Karthik K added a comment - As mentioned in person - THRIFT-363 actually publishes mvn artifacts that can be used with both mvn and ivy. So for now - we can help check to publish mvn repository to a location of our choice and see if we would be able to integrate with thrift.
          Hide
          stack added a comment -

          Making this a blocker as reminder to self to do this soon, at least thrift.

          Show
          stack added a comment - Making this a blocker as reminder to self to do this soon, at least thrift.
          stack made changes -
          Priority Major [ 3 ] Blocker [ 1 ]
          Karthik K made changes -
          Link This issue depends on HADOOP-6617 [ HADOOP-6617 ]
          Hide
          Karthik K added a comment -

          For artifact publishing of hadoop

          Show
          Karthik K added a comment - For artifact publishing of hadoop
          Karthik K made changes -
          Link This issue depends on HBASE-2099 [ HBASE-2099 ]
          Hide
          Karthik K added a comment -

          'Maven'ization helps this process.

          Show
          Karthik K added a comment - 'Maven'ization helps this process.
          Karthik K made changes -
          Link This issue depends on HADOOP-6382 [ HADOOP-6382 ]
          John Sichi made changes -
          Link This issue blocks HIVE-1235 [ HIVE-1235 ]
          Karthik K made changes -
          Link This issue depends on HBASE-2309 [ HBASE-2309 ]
          Hide
          Karthik K added a comment -

          zk 3.3.0 is going to be released soon, with mvn artifacts., as seen from the latest update to zk ticket.

          HBASE-2255 discusses the artifact for the patched version of hadoop (hdfs sync + others) as needed by hbase , that I believe, would eventually be available in a public repository, say - groupId - org.apache.hbase and artifactId - "hadoop-0.20.2-patched" , say..

          As before - THRIFT-363 is pending still.

          Show
          Karthik K added a comment - zk 3.3.0 is going to be released soon, with mvn artifacts., as seen from the latest update to zk ticket. HBASE-2255 discusses the artifact for the patched version of hadoop (hdfs sync + others) as needed by hbase , that I believe, would eventually be available in a public repository, say - groupId - org.apache.hbase and artifactId - "hadoop-0.20.2-patched" , say.. As before - THRIFT-363 is pending still.
          Hide
          Karthik K added a comment -

          zk 3.3.0 now published to mvn repositories. HBASE-2392 takes care of the upgradation.

          THRIFT-363 is checked in now too. So , eventually thrift team will publish their artifacts as well.

          So - all decks cleared for hbase mvn repository publishing here , when it we do a 0.21.0 release.

          Show
          Karthik K added a comment - zk 3.3.0 now published to mvn repositories. HBASE-2392 takes care of the upgradation. THRIFT-363 is checked in now too. So , eventually thrift team will publish their artifacts as well. So - all decks cleared for hbase mvn repository publishing here , when it we do a 0.21.0 release.
          Hide
          stack added a comment -

          @Kay Kay You a have a patch so we can start publishing snapshots now?

          Show
          stack added a comment - @Kay Kay You a have a patch so we can start publishing snapshots now?
          Hide
          Karthik K added a comment -

          @stack: Will look into the patch over the weekend. Given that we are already in maven , I believe it should not be very hard from now.

          Show
          Karthik K added a comment - @stack: Will look into the patch over the weekend. Given that we are already in maven , I believe it should not be very hard from now.
          Hide
          Lars Francke added a comment -

          In HBASE-2394 we are currently working on using the parent Apache pom which already has the necessary repositories defined as far as I know so it should be easier to publish jars after that has been finished.

          Just a heads up to avoid duplicate work.

          Show
          Lars Francke added a comment - In HBASE-2394 we are currently working on using the parent Apache pom which already has the necessary repositories defined as far as I know so it should be easier to publish jars after that has been finished. Just a heads up to avoid duplicate work.
          Hide
          Karthik K added a comment -

          Thanks Lars for the heads -up. That would definitely address some of the presence of xml tags as needed by the repo publication process. Any idea - how far are we in that process. Let us know.

          Otherwise- I was planning to modify the <dependencyManagement> .. </dependencyManagement> with 1 entry for HBase publishing and a writable-user name, that any of you committers can override in ~/.m2/settings.xml to start publishing for snapshots for the moment.

          Let me know your thoughts on the same.

          Show
          Karthik K added a comment - Thanks Lars for the heads -up. That would definitely address some of the presence of xml tags as needed by the repo publication process. Any idea - how far are we in that process. Let us know. Otherwise- I was planning to modify the <dependencyManagement> .. </dependencyManagement> with 1 entry for HBase publishing and a writable-user name, that any of you committers can override in ~/.m2/settings.xml to start publishing for snapshots for the moment. Let me know your thoughts on the same.
          Hide
          stack added a comment -

          .bq Otherwise- I was planning to modify the <dependencyManagement> .. </dependencyManagement> with 1 entry for HBase publishing and a writable-user name, that any of you committers can override in ~/.m2/settings.xml to start publishing for snapshots for the moment.

          Above sounds good to me Kay Kay.

          Show
          stack added a comment - .bq Otherwise- I was planning to modify the <dependencyManagement> .. </dependencyManagement> with 1 entry for HBase publishing and a writable-user name, that any of you committers can override in ~/.m2/settings.xml to start publishing for snapshots for the moment. Above sounds good to me Kay Kay.
          Hide
          Karthik K added a comment -

          1. Create a settings.xml as outlined in the patch.

          2. Place it by default in ~/.m2/settings.xml (preferred) or in a custom location and specify the same as input using the -s option

          3. Invoke the deploy target

          $ mvn -s settings.xml deploy

          Target url-s copied from apache parent pom ( version 7)

          Private distributionManagement url-s removed, since I believe they were needed for zk / thrift publishing and not needed anymore.

          Show
          Karthik K added a comment - 1. Create a settings.xml as outlined in the patch. 2. Place it by default in ~/.m2/settings.xml (preferred) or in a custom location and specify the same as input using the -s option 3. Invoke the deploy target $ mvn -s settings.xml deploy Target url-s copied from apache parent pom ( version 7) Private distributionManagement url-s removed, since I believe they were needed for zk / thrift publishing and not needed anymore.
          Karthik K made changes -
          Attachment HBASE-1933.patch [ 12441272 ]
          Karthik K made changes -
          Status Open [ 1 ] Patch Available [ 10002 ]
          Hide
          Karthik K added a comment -
          I was planning to modify the <dependencyManagement> .. </dependencyManagement>

          Oops - meant to say <distributionManagement> .

          Show
          Karthik K added a comment - I was planning to modify the <dependencyManagement> .. </dependencyManagement> Oops - meant to say <distributionManagement> .
          Hide
          stack added a comment -

          I committed the above patch. Its doing something, publishing something here: https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/

          But something is up still... trying to figure it (w/ Kay Kay's help). Added 'deploy' to hudson build targets. Hopefully hudson user can deploy to mvn repo for us. #2010 build will tell us.

          Show
          stack added a comment - I committed the above patch. Its doing something, publishing something here: https://repository.apache.org/content/repositories/snapshots/org/apache/hbase/ But something is up still... trying to figure it (w/ Kay Kay's help). Added 'deploy' to hudson build targets. Hopefully hudson user can deploy to mvn repo for us. #2010 build will tell us.
          Hide
          Karthik K added a comment -

          The artifacts published to the apache snapshot repositories looks ok. (hbase-core , hbase-contrib-stargate-core , hbase-contrib-transactional would be needed by most users).

          The patch contains 'apache standard' server ids ( as in the pom.xml of apache ) so hoping that appropriate server ids are set up in the hudson environment, that will 'deploy' . As stack mentioned above - keeping fingers crossed until then.

          Show
          Karthik K added a comment - The artifacts published to the apache snapshot repositories looks ok. (hbase-core , hbase-contrib-stargate-core , hbase-contrib-transactional would be needed by most users). The patch contains 'apache standard' server ids ( as in the pom.xml of apache ) so hoping that appropriate server ids are set up in the hudson environment, that will 'deploy' . As stack mentioned above - keeping fingers crossed until then.
          Hide
          Karthik K added a comment -

          An username with write access to 'org.apache.hbase' groupId is required for deploy to succeed. INFRA-2609 , raised with nexus/hudson infrastructure to seek best practices and use appropriately.

          Show
          Karthik K added a comment - An username with write access to 'org.apache.hbase' groupId is required for deploy to succeed. INFRA-2609 , raised with nexus/hudson infrastructure to seek best practices and use appropriately.
          Hide
          Karthik K added a comment -

          As per update on INFRA-2609 , the machines should have been configured to publish to all groupId under org.apache.* . So - may be - we are good here for an automatic deploy.

          Show
          Karthik K added a comment - As per update on INFRA-2609 , the machines should have been configured to publish to all groupId under org.apache.* . So - may be - we are good here for an automatic deploy.
          Hide
          Karthik K added a comment -

          Yes. It (hudson deploy) works.

          1211 ( http://hudson.zones.apache.org/hudson/view/HBase/job/HBase-Patch/1211/console ) uploads the artifacts successfully after running the tests. Great.

          Show
          Karthik K added a comment - Yes. It (hudson deploy) works. 1211 ( http://hudson.zones.apache.org/hudson/view/HBase/job/HBase-Patch/1211/console ) uploads the artifacts successfully after running the tests. Great.
          Hide
          stack added a comment -

          Closing. Our successful hudson builds are now dumped into the apache m2 snapshot repository. Thanks to those that made this possible.

          Show
          stack added a comment - Closing. Our successful hudson builds are now dumped into the apache m2 snapshot repository. Thanks to those that made this possible.
          stack made changes -
          Status Patch Available [ 10002 ] Resolved [ 5 ]
          Assignee stack [ stack ] Kay Kay [ kaykay.unique ]
          Resolution Fixed [ 1 ]
          Hide
          Sergey Kabashnyuk added a comment -
          Show
          Sergey Kabashnyuk added a comment - 0.20.4 HBASE jars missed on http://repo2.maven.org/maven2/org/apache/hadoop/
          Hide
          stack added a comment -

          Sergey, our TRUNK is maven build, not the branch 0.20.4 was made from. We don't have a pom for 0.20 branch. We could hand-publish it I suppose if someone spent some time on a pom.

          Show
          stack added a comment - Sergey, our TRUNK is maven build, not the branch 0.20.4 was made from. We don't have a pom for 0.20 branch. We could hand-publish it I suppose if someone spent some time on a pom.
          Gavin made changes -
          Link This issue depends on HADOOP-6617 [ HADOOP-6617 ]
          Gavin made changes -
          Link This issue depends upon HADOOP-6617 [ HADOOP-6617 ]
          Gavin made changes -
          Link This issue depends on HBASE-2099 [ HBASE-2099 ]
          Gavin made changes -
          Link This issue depends upon HBASE-2099 [ HBASE-2099 ]
          Gavin made changes -
          Link This issue depends on HADOOP-6382 [ HADOOP-6382 ]
          Gavin made changes -
          Link This issue depends upon HADOOP-6382 [ HADOOP-6382 ]
          Gavin made changes -
          Link This issue depends on HBASE-2309 [ HBASE-2309 ]
          Gavin made changes -
          Link This issue depends upon HBASE-2309 [ HBASE-2309 ]

            People

            • Assignee:
              Karthik K
              Reporter:
              Cyril Lakech
            • Votes:
              7 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development