Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: domain of sebbaz@gmail.com designates
 209.85.220.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPFNckgzbObOw3tq2DCFN7f3hMHDZoPcrKG93+U-Yp8u+_71GA@mail.gmail.com>
References: 
 <CAOGo0VZCKvUxhTE8yAMsP3nU0Y6utJJ3J49VRXw3h3pUWDogMQ@mail.gmail.com>
	<5325792.13164.1325942464609.JavaMail.mobile-sync@iaid9>
	<-1053654366337853783@unknownmsgid>
	<4F08A08D.1040306@free.fr>
	<9AC53AB0-090F-486E-B732-DD93855E6E05@dslextreme.com>
	<CAPFNckgzbObOw3tq2DCFN7f3hMHDZoPcrKG93+U-Yp8u+_71GA@mail.gmail.com>
Date: Sun, 8 Jan 2012 11:23:54 +0000
Message-ID: 
 <CAOGo0VY4wKkVTkiZkVhMd4_B9p56MBDiOJoa+18-22SAREMc0Q@mail.gmail.com>
Subject: Re: [ALL] Maven 2 - (was Commons Parent pom - any more changes
 needed?)
From: sebb <sebbaz@gmail.com>
To: Commons Developers List <dev@commons.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 8 January 2012 11:11, Christian Grobmeier <grobmeier@gmail.com> wrote:
> On Sun, Jan 8, 2012 at 6:21 AM, Ralph Goers <ralph.goers@dslextreme.com> =
wrote:
>>
>> On Jan 7, 2012, at 11:44 AM, Luc Maisonobe wrote:
>>
>>> Le 07/01/2012 15:36, Gary Gregory a =E9crit :
>>>>>
>>>>
>>>> When can we drop support for M2?
>>>
>>> I guess there are still a lot of m2 users, and for the next few years
>>> there will still be many. At least when I run an "aptitude search maven=
"
>>> on my Debian Linux box, I only see maven 2 supported. Getting rid of
>>> maven 2 is not an option for me now.
>>
>
> Out of curiosity: why can't you run m3 on debian linux? m3 is java,
> you should be able to download it and place it in your path.
> I thought everybody who wants to build commons components himself
> should be able to install m3 on every plattform with java around. Or
> do I miss something?

I think what everyone is missing is that CP22 (now) works fine with M2.
The .svn issue was a red herring, because it also affects M3 when
using a SVN 1.7 client.

However, Commons Parent does not (yet) work properly with M3, e.g.
problems with non-Nexus deployment.

>> I'm not sure how it is relevant whether commons users use maven 2 or 3. =
Even if we require Maven 3 to build a commons component anyone can still us=
e it in a Maven 2 build. They only would require Maven 3 if they actually w=
ant to build one of our artifacts on their own.
>

But remember that the ASF releases source, so we cannot arbitrarily
change build procedures without at least considering how that might
affect downstream users.

> +1
>
> Cheers
> Christian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>

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