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, 14 Jan 2010 02:36:54 GMT

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

Paul Smith commented on HBASE-2099:

I think this is where Maven starts to pay off, just by adding this snippet in the top-level

      <id>Apache Public Releases</id>
      <id>Apache Public Snapshots</id>
      <name>Aconex Snapshots</name>
      <id>HBase Site</id>

and having a corresponding username/password entries in my ~/.m2/settings.xml for each id,
I can do this:

# skip tests because they're currently failing in this interim

mvn -Dmaven.test.skip.exec=true deploy site:deploy

Imagine that the Snapshots url is the real Apache Snapshots location, this is a fast way of
providing working snapshot builds for upstream people to use without a full release:


Also the site generation (putting aside it's ugliness) does produce useful info:


A full release can then use the maven-release-plugin, which will manage the SCM tagging, and
pushing the final release candidates direct to their proper location on the Apache central
release repo.

> 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.3.full.patch,
HBASE-2099.3.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.

View raw message