[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801726#action_12801726
]
Lars Francke commented on HBASE-2099:
-------------------------------------
Very good work. I'm looking forward to building HBase with Maven.
One thing though: You've added a dependency for Thrift but that will perhaps
never come to a Maven repository.
Could you have a look at HBASE-1360?
We basically need three new dependencies for the core for now (at least for
0.21): slf4j-simple 1.5.8, slf4j-api 1.5.8 (I've seen that you added that
already for avro) and commons-lang 2.4. And the libthrift-0.2.0.jar file from
the lib/ directory, which you mention should be installed to the local
repositories (mvn install:file/Nexus) but it would be ideal if Maven could use
the jar from the lib directory directly for now without this additional step.
> 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.5.patch, HBASE-2099.6.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.
