Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of kaykay.unique@gmail.com
 designates 209.85.223.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=s3E/H6ZXVwAqHrpZoJmBiw1678VAcOplFRzdoOzAWo1jf/23UJmaUqK01R2/JuL5zW
         Ej4M2feSW19fcB54UIHjugWuV0dmid5gvc64he8jJv9ZYRP2IUVWzkkMdNhaZoKO8k9R
         y8ERjnHXuO86KxCGAjMiC1oAPM6bmF3J6liAk=
Message-ID: <4B766212.5020506@gmail.com>
Date: Sat, 13 Feb 2010 00:25:54 -0800
From: Kay Kay <kaykay.unique@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
 rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
To: hbase-dev@hadoop.apache.org
Subject: Re: Moving to Maven (HBASE-2099)
References: <3741C613-B9B6-4472-961A-608B30FA049F@aconex.com>
	 <4B765BFD.2080103@gmail.com>
	 <1c5747851002130003r2da1b8d2sc1bff83426e786f3@mail.gmail.com>
 <78568af11002130010g4bb8682clc024ae1816c52e16@mail.gmail.com>
In-Reply-To: <78568af11002130010g4bb8682clc024ae1816c52e16@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Mathias -
    I have been using Ivy / Maven , interchangeably in different 
projects for the build management.  Both of them clearly have their 
strong points and drawbacks.  Ivy fits great for thrift because of the 
nature of tasks , involved using some external command-line (thrift 
generators) etc.  As I mentioned before - HBase does not have such cross 
maven goals / between the hairs as the build lifecycle is pretty 
straight-forward.
   In any case - the intention is to get to publish HBase artifacts and 
maintain a smaller core and encouraging contribs. from the artifacts as 
opposed to getting into the codebase.
Once there are HBase artifacts published , the contrib / plugins for the 
same would be free to use ivy (with m2compatible="true") / maven as 
appropriate.

Ryan -
    The slowness is attributed to the 'changing="true" ' in ivy.xml-s 
for all the hadoop-common / -hdfs / -mapreduce snapshots that we are 
using. I am facing similar 'slowness' with other mvn hadoop (snapshot) 
dependencies as well. In retrospective, that should have been made a 
configurable flag in libraries.properties , to ease things. Hopefully 
that is sorted out soon.


On 02/13/2010 12:10 AM, Ryan Rawson wrote:
> Would you mind elaborating more?  At the moment, most people do not
> build hbase, and the POM/jar/publishing thing is orthogonal - those
> who wish to build their own projects with ivy and/or ant are free to
> do so and not be impacted by our use of maven.
>
> We have ivy, but it doesnt integrate with our IDEs and is rather slow
> to build and rebuild.
>
> On Sat, Feb 13, 2010 at 12:03 AM, Mathias Herberts
> <mathias.herberts@gmail.com>  wrote:
>    
>> -1
>>
>> I think Maven is too complex and will lower the adoption of HBase by
>> people today willing to build it.
>>
>> I would suggest using Ivy for dependency management as was done in Thrift.
>>
>> Mathias.
>>
>>