[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803091#action_12803091
]
stack commented on HBASE-2099:
------------------------------
nm. pilot error (I'd double applied the patch so xml files were doubled).
So, I got further. Had to set MAVEN_OPTS="-Xmx1024m" else it was OOMEing.
Build is failing on me because I just updated us to thrift 0.2.0. I'm putting
commons-lang in wrong place. I added version property up in the top-level pom
and then added the commons-lang dependency to core/pom.xml but that doesn't
seem to be enough for the compile of the thrift generated classes. They fail
to compile looking for HashCodeBuilder from commons-lang. What would you
suggest?
Paul, I think that I could make this work with your sweet instructions, no
problem. Whats missing is the vote on the move to maven. One thing I was
thinking was that we could bring up "move to maven" as a topic at next weeks
HUG. One of us could talk it up for you but for sure you should start the
discussion going up on the list.
Great stuff Paul.
> 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 Move Script.txt, HBASE-2099.5.patch, HBASE-2099.6.patch,
> HBASE-2099.7.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.
