I suspect the problems I'd like to avoid we've already mostly taken on
with Ivy. Primarily: The need to be connected to build and test. That is
a real problem on a 15 hour flight. Domestic flights have options, but
not the international ones. At least with Ivy I can edit out the resolve
steps from the Ant buildfile as long as I ran 'ant test' before boarding.
Edit, then rm -rf build/classes/* instead of 'ant clean', etc.
Don't tell me I need to spend hours to figure out how to set up a local
mirror of the public repo and then keep it up to date thereafter. There
seem to be 5 large repositories referenced in ivysettings.xml. I doubt I
have or can spare enough disk on the laptop and don't have the bandwidth
to prune to just the packages that HBase needs and then update by hand
whenever that changes or they change. If you tell me this, I have an
impolite response for you.
Clearly I'm unhappy with the definition of "progress" of some. Will
Maven make me more or less unhappy? If Maven can support some totally
disconnected operation from cache -- which Ivy cannot apparently -- then
that would be awesome. If it makes the situation for me worse, I'll just
do something else on those flights.
- Andy
----- Original Message ----
> From: Ryan Rawson <ryano...@gmail.com>
> To: hbase-dev@hadoop.apache.org
> Sent: Sat, February 13, 2010 12:10:36 AM
> Subject: Re: Moving to Maven (HBASE-2099)
>
> 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
> 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.
> >
