hbase-dev mailing list archives

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

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

stack commented on HBASE-2099:
------------------------------

Looking at the lightweight patch:

+ Our groupid is org.apache.hbase.  I think that should be org.apache.hadoop.hbase.  Will
this groupid put us into the right relative location in the apache maven repo?  Here's apache
snapshots: https://repository.apache.org/content/repositories/snapshots/org/apache/hadoop/.
 We should be going into this directory I'd say.
+ The artifactid for core is hbase-core.  Currently our hbase jar is named hbase-X.X.X.jar.
 if artifactId is hbase-core, doesn't that mean the core jar will be named hbase-core-X.X.X.jar.
 Can we keep our old name?  Maybe the parent artifactId could be hadoop-hbase and then this
core module's could be plain hbase?
+ On these:

{code}
+    <zookeeper.version>3.2.2</zookeeper.version>
+    <thrift.version>r771587</thrift.version>
{code}

Can't we just check these in?  I remember that in maven for certain dependencies, you could
override the pull from a remote repository and instead have it read from a local directory.
 Is that still so?  (I might be remembering this wrong).

+ We can add in licensing and better project description stuff later, no worries.

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


Mime
View raw message