hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: Moving to Maven (HBASE-2099)
Date Sun, 14 Feb 2010 02:49:59 GMT
I have previously uploaded most the hbase objects to github.  I can give
whomever commit access...

On Feb 13, 2010 6:02 PM, "Paul Smith" <psmith@aconex.com> wrote:

On 13/02/2010, at 6:59 PM, Kay Kay wrote:

> +1 on the 'maven'ization.
> As far as I see - there...
Yep, I think HBase definitely is a standard project type that fits the
intent that Maven was originally designed for.  There's no question, if a
project has a non-standard requirement, then going down a Maven path could
be tricky.  But HBase is nice and simple, and standard.

> As I had suggested earlier - the best course of action, for a smooth
transition would be -
> *...
sounds good, so keep the ivy part tracking the Maven changes (basically a
side-by-side approach) until a final switch?

It might be worth setting up a branch too for visibility prior to a
commit/merge to trunk (I don't recommend a merge under SVN for sure, GIT
probably handles that way better).


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message