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 Tue, 12 Jan 2010 23:26:54 GMT

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

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

the more I look into this the more I think I _could_ hack up a Maven structure that 'works'
following the same pattern I had done for core, which is to create a dummy directory containing
the pom.  But that sort of smells.

What I'd prefer to be done would be this

# Move src/contrib -> contrib, have a top level contrib/pom.xml that makes this tree a
multi-module project
# Move src/java -> core/src/java
# Move src/test -> core/src/test (probably extract out of this a core/src/resources too,
but may be possible to configure the resource plugin to filter out .java and use the same
directory, not ideal though)
# Move src/test/data -> core/test/resources

The src/webapps directory is interesting, I'm not exactly sure where that is supposed to be
bundled up.  But I can definitely see how we can use the assembly plugin and descriptors to
create the overarching tar ball for release purposes to mimic the current distribution.

This sort of proposal is obviously far more invasive.  If there was a wish to have the Ivy
setup in place in the interim, that would have to be modified to keep track.

What about I just go and fiddle with the current setup and just show it in a fully working
setup and upload it here as an example.


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


Mime
View raw message