Move build to Maven
-------------------
Key: HBASE-2099
URL: https://issues.apache.org/jira/browse/HBASE-2099
Project: Hadoop HBase
Issue Type: Task
Reporter: stack
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.
