hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Wed, 13 Jan 2010 04:53:54 GMT

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

stack commented on HBASE-2099:

Here's a few comments Paul (Thanks for taking this on).

That the generated jar, hbase-0.21.0-dev.jar, has a hbase-default.xml in top-level and in
a conf subdir looks wrong.  I think the top-level one is the one we want.  Whatever, its not
your prob. Just make an issue on it and one of us will figure it.

.bq Maven appears to locate some .java files from within the zookeeper dependency...

Its finding java files in the zk jar and compiling them?

.bq The ivy-generated jar contains pre-compiled JSP file...

Yeah.  HBase and Hadoop do this.  I think its so hadoop/hbase can run on a jre, that they
don't require a jdk.

.bq cidentally the saveVersion.sh could probably be replaced with a text replace during a
Maven build cycle...


On moving dirs, thats no problem (Can't make an omelette...)

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

View raw message