[jira] Updated: (HBASE-2099) Move build to Maven

["Paul Smith (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Smith updated HBASE-2099:
------------------------------

    Attachment: HBase Move Script.txt
                HBASE-2099.8.patch

Latest patch and move script based on latest trunk, just wanted to re-sync since I've been out of action with some family health issues (all good now).

* adjusted to take the new libthrift-0.2.0.jar, that's been deployed to my 'paul special' repository
* Found missing step to actually 'svn add' the newly patched in poms
* added svn:ignore entries for Maven's target directory (can't find a simple way to add a line via 'svn propset' non-interactively, probably could do this with a 'svn proplist' via awk, and then add a line, but honestly it's just easier if someone types it in via vi or something.. :) Lazy! )

the assembly tar ball is 'working' although I can't quite get the sources to sit properly as a jar, they keep unpacking themselves inside the tar ball, may need an email to the maven-user list, it's not something I've done before, definitely solvable, just not obvious right this second.  I'm sure someone will not like the tar ball directory layout, but we can talk.

Still have the other contrib modules to add, and there's that one test case that fails for some reason, but inching along..



> 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.7.patch, HBASE-2099.8.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.