Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@incubator.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Message-ID: <20070503105436.vb0pfovfsowcswo8@www2.digizenstudio.com>
Date: Thu, 03 May 2007 10:54:36 -0400
From: Jing Xue <jingxue@digizenstudio.com>
To: ivy-user@incubator.apache.org
Subject: Re: ApacheCon news ?
References: <EF39D77A486C234B9D9933091CE6D21EDAF3F7@z011034.bk.fin.local>
	<635a05060705030354v2834385fs5743bd5cfdcc500@mail.gmail.com>
In-Reply-To: <635a05060705030354v2834385fs5743bd5cfdcc500@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=UTF-8;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)


Quoting Xavier Hanin <xavier.hanin@gmail.com>:

> People seemed interested, and there is a question occuring pretty
> frequently in ApacheCon: could we get closer to maven, and either
> reuse stuff from their code base, or the other way around, use Ivy as
> the dependency management engine for Maven.
>
> This is something interesting IMO, but another hand I don't think we
> are big enough for the moment to get enough energy to go int his
> direction. I'd prefer to first concentrate on building a rock solid
> 2.0 version with even better ant integration, and then once we get
> graduated and released, see if we can concentrate energy on this
> focus... unless someone want to contribute stuff in this direction.

+1

I for one would vote for the Ant+Ivy bundling - maybe not the default =20
distribution but some "deluxe edition" or something :-).  I'm not sure =20
how much value Ivy can contribute to Maven, on the other hand. =20
Dependency/repository management isn't the weakness of Maven.

--=20
Jing Xue