Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of phil.steitz@gmail.com designates
 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=QmtRJD+VbmfkcMEmsep8XxZpBJ8EfBjTiDA6qIE73C1ESo2Spc9QLrnUfpqtnNazfzioor3EjS2QrM2YExWtWjG5UMFaJxb9z4Iz53V83PuWw61+0oyQgNVHczAq+zY3k25hS+7wiEguG9+iT2ylkFP/XY6u85IQs11ckZ2DlBg=
Message-ID: <8a81b4af0610152233u758c19fbn20fa507e03252255@mail.gmail.com>
Date: Sun, 15 Oct 2006 22:33:30 -0700
From: "Phil Steitz" <phil.steitz@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [vfs][all] move vfs to maven 2 to setup a vfs-sandbox
In-Reply-To: <453085D7.6080808@ops.co.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <452FAE1F.2080306@ops.co.at>
	 <98e4f1cd0610131456x12b270e9y6e3b7628220b65c2@mail.gmail.com>
	 <453085D7.6080808@ops.co.at>

On 10/13/06, Mario Ivankovits <mario@ops.co.at> wrote:
> Hi Torsten!
> > ...so the real question is "is it ok to have a proper component use
> > maven2" ...right?
> hehe .... didn't I ask this?
> Yes, thats the real question!
>
> As a compromise I can maintain the maven 1 build for the core only
> (using the maven 2 directory layout), and a maven 2 build for the
> core/sandbox stuff.
> That also allows me to e.g. build the site with maven 1 as long as
> Commons haven't moved to maven 2 at all.
>
I think its perfectly fine for individual components, both proper as
well as sandbox, to start moving to maven 2.  We did a lot of work
several years back to get to a common look and feel for the site and a
decent level of build standardization using maven 1 and we are not
quite there yet in maven 2; but I think the best way for us to get
there is to start developing m2 builds, which will force us to solve
the remaining problems.To make it less painful for users during
transition, keeping a working m1 build for some time is a good idea;
but I would recommend making a clean break soon - certainly by the
time you cut the release.  More valuable than keeping an m1 build
around indefinitely is a working Ant build, IMO.

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org