hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Smith (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Thu, 21 Jan 2010 02:00:54 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803124#action_12803124
] 

Paul Smith commented on HBASE-2099:
-----------------------------------

ok, well my MAVEN_OPTS is < 1024, but is greater than default, I was using -Xmx512 because
our own corporate packaging requires it.

I'll note that down in the plan though, I'll be curious to know where it barfs through lack
of memory because HBase build system isn't too large.

bq. 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?

well that should work, can you send me the top-level pom and core/pom.xml you are using? 
where would I get thrift 0.2.0 from?  Is this stuff in trunk already or is it in a private
work area?

I'll start drafting a note to hbase-dev anyway.

> 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.


Mime
View raw message