hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kay Kay (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Fri, 22 Jan 2010 00:38:54 GMT

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

Kay Kay commented on HBASE-2099:
--------------------------------

| You want us to patch thrift 0.2.0 with thrift-363? Then you want me to set up a mvn repo
up on people.apache.org/~stack.

Sure. If you have the source code of thrift-0.2.0 - you can apply the patch in THRIFT-363
( the latest one ) and see if you are able to publish the artifacts. 

Caveat: 


+  <property name="apache.snapshot.repository" value="https://repository.apache.org/content/repositories/snapshots"
/>

This property needs to be overridden / changed to a url that can publish to the home directory
(people.apache.org/~username ) . 

Aliter: 
--------
This patch should install the package in ~/.m2/repository in the local disk  and the installed
files can be manually copied (ftp-ed) to the path mentioned above.  
(We can go down this route , if figuring out the url to publish to people.apache.org/~username
is harder ). 



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


Mime
View raw message