[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799928#action_12799928
]
Paul Smith commented on HBASE-2099:
-----------------------------------
Thanks @stack. There is no question that if a project has a non-standard need,
then using Maven is a bit of the classic square-peg-round-hole scenario.
But it's surprising how when one looks at builds needs, the commonality is
usually there. Yes, with Maven you really do need to give up a little
flexibility (one can make an existing structure work with Maven, but it's
usually easier to just conform). The advantage to conformity is the principle
of standardization; a common build system principle means that more people
will understand how to use it, ("Hey, I've used Maven projects before, so this
one is easy to follow").
I haven't spotted anything in the Hbase environment as yet that is really
'non-standard'. You're building a series of JARs, and packaging them up into a
tar ball, that's pretty vanilla flavoured as Maven builds go, and exactly what
it was targetted for.
Ivy has a nice sweet spot of being familiar to those with Ant experience, and
it does foster some of the commonality Maven strives towards.
At the end of the day, this must be driven from the hbase-dev community. I'm
happy to provide an example working setup based on my experience for
consideration, and if it is not needed, it's no biggie.
> 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: HBASE-2099.2.full.patch, HBASE-2099.2.patch,
> HBASE-2099.patch
>
>
> 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.
