[
https://issues.apache.org/jira/browse/HBASE-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797914#action_12797914
]
Kay Kay commented on HBASE-1933:
--------------------------------
| 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.
> Upload Hbase jars to a public maven repository
> ----------------------------------------------
>
> Key: HBASE-1933
> URL: https://issues.apache.org/jira/browse/HBASE-1933
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: Cyril Lakech
> Assignee: stack
> Fix For: 0.21.0
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
