[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830778#action_12830778
]
Paul Smith commented on HBASE-2099:
-----------------------------------
bq. Yes. As far as zookeeper is concerned - it will be available soon in a
maven snapshot repository with the next release. As far as thrift is concerned
- we can publish ourselves once a groupId is identified for hbase.
The Maven Release plugin is absolutely brutally anal about snapshot
dependencies though. It will not let you 'mvn release' a project such as HBase
if that project depends on snapshot artifacts. There's good reasons for it,
but there's no flexibility built in. I'm hoping that Zookeeper can be deployed
to a non-snapshot status (which is sort of by definition maven central..)
I'm sure that since Zookeeper is pushing it's own releases, it won't take too
much effort to get Zookeeper 3.2.2 in Maven central.
Thrift is still the sticking point, the fact it's an incubation project makes
life difficult. That doesn't mean you can't deploy a non-snapshot version of
the artifact to a known repository (even Stack's own one), you just won't be
able to take advantage of the Nexus staging and deployment into central that
Sonatype is offering.
> Move build to Maven
> -------------------
>
> Key: HBASE-2099
> URL: https://issues.apache.org/jira/browse/HBASE-2099
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: stack
> Attachments: findbugs.html, findbugs.html, HBase Move Script.txt,
> HBASE-2099.9.patch, test-reports.zip
>
>
> This issue is for discussing pros and cons of moving hbase build to Apache
> Maven.
> Maven, if you take on its paradigm, does a lot for you. There are also a
> bunch of nice plugins that do nice reports on state of project; findbugs,
> that nice plugin where you can give out urls that will resolve to lines in
> source code (a doxygen-like thing ... I've forgotten its name). Other
> examples are a docbook plugin that would do the build inline with doc build.
> We could start up the hbase book using docbook format and the hbase book
> would ride along with versions.
> As I see it -- and its a while since I've done this stuff so things may have
> since changed -- in the way of an easy move to maven is our src/contrib
> content. Maven would have these as distinct projects pulling in their hbase
> dependency or, if you wanted to take on the maven subproject notion, then,
> hbase would be at same level in build as the contribs -- it would be a
> subproject too just built before the others.
> Anyone interested in working on this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
