[
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.6.patch
This patch now makes decent headway into creating a overarching Hbase
project-level binary (that's the src/assembly/bin.xml descriptor).
Attached:
# latest patch, now actually USABLE with 'patch -p0' etc. Not sure why svn
diff doesn't output new files correctly, but there you go.
# 'plan' script showing the steps to execute to get to this point, which is a
poor-mans version of Git I'm sure.
# example top-level binary distribution (not including _everything_ yet, but
looking close to the current setup)
Basically:
# Take a clean HBase-trunk checkout
# execute the steps included in the plan (but change the path to the patch)
note: I'm _positive_ this will not compile unless you have a local Nexus Maven
repository setup, because I haven't specified the snapshot & google-code repo's
in the top-level pom as yet, without these specified, and without a local
repository manager proxying them, the dependencies won't be found.
That's next on my list.
However, if I:
{noformat}
mvn -Dmaven.test.skip.exec=true package assembly:assembly
{noformat}
I find a tar.gz file in the hbase-trunk/target directory, which if unpacked,
and then:
{noformat}
target/hbase-0.20.2-SNAPSHOT-bin/bin/start-hbase.sh
{noformat}
seems to start Hbase (at least no NoClassDefFoundErrors anyway, I think I have
an existing Hbase service running it doesn't like).
> 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-2099.5.patch, HBASE-2099.6.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.
