[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803477#action_12803477
]
stack commented on HBASE-2099:
------------------------------
That was it for me.
{code}
[INFO] Building tar :
/Users/stack/checkouts/hbase/trunk/target/hbase-0.20.2-SNAPSHOT-bin.tar.gz
[INFO]
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ------------------------------------------------------------------------
[INFO] HBase ................................................. SUCCESS
[1:38.680s]
[INFO] HBase Core ............................................ SUCCESS
[1:03.140s]
[INFO] HBase Contrib ......................................... SUCCESS [0.005s]
[INFO] HBase Contrib - Stargate .............................. SUCCESS [37.954s]
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 3 minutes 23 seconds
[INFO] Finished at: Thu Jan 21 12:12:17 PST 2010
[INFO] Final Memory: 55M/153M
[INFO] ------------------------------------------------------------------------
{code}
The resulting tar ball is pretty dang close. The lib dir is a bit
overpopulated methinks but would have to check. The resultant jar is named
hbase-core:
-rwxr-xr-x 1 stack staff 1583331 Jan 21 12:10
hbase-core-0.20.2-SNAPSHOT.jar
We need to get test jar in there too.
Hadoop-style is to ship the source all in the one tar ball but maven does bin
and src tarballs. Thats fine by me separating them.
I ran with tests and all output shows on console. We can fix that later?
Stargate seems to be the only contrib. Is that intentional? Thats fine if it
is.
Whats under the contrib dir needs work but can do that later.
I tried to build the site and got this:
{code}
Missing:
----------
1) org.apache.hadoop.hbase:hbase-core:jar:0.20.2-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.hadoop.hbase
-DartifactId=hbase-core -Dversion=0.20.2-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.hadoop.hbase
-DartifactId=hbase-core -Dversion=0.20.2-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.hadoop.hbase:hbase-contrib-stargate:jar:0.20.2-SNAPSHOT
2) org.apache.hadoop.hbase:hbase-core:jar:0.20.2-SNAPSHOT
----------
1 required artifact is missing.
{code}
This is looking great Paul.
> 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.7.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.
