Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 64845 invoked from network); 29 Sep 2005 01:02:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Sep 2005 01:02:55 -0000 Received: (qmail 74972 invoked by uid 500); 29 Sep 2005 01:02:53 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 74907 invoked by uid 500); 29 Sep 2005 01:02:53 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 74894 invoked by uid 99); 29 Sep 2005 01:02:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 18:02:53 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of foamdino@gmail.com designates 64.233.184.205 as permitted sender) Received: from [64.233.184.205] (HELO wproxy.gmail.com) (64.233.184.205) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Sep 2005 18:02:58 -0700 Received: by wproxy.gmail.com with SMTP id i13so2918wra for ; Wed, 28 Sep 2005 18:02:30 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer; b=hF6+B79+G9PVf73Awctn20sdCNjc0t1N4GXvE3hx8pxEzNFe0x/+BO3pYrRZ69yPh2gMR+RVNvJHi5Camrird7bKsHNEtlbWLLZMeilJv7H6bN7dwuIwnwuQ2AJ9Wh0tVkub5nwiqWohslXfBrIhkVkAgVryVYEbigGiVzWnfUE= Received: by 10.54.34.1 with SMTP id h1mr250293wrh; Wed, 28 Sep 2005 18:02:30 -0700 (PDT) Received: from ?221.132.35.193? ( [221.132.35.193]) by mx.gmail.com with ESMTP id 35sm86543wra.2005.09.28.18.02.28; Wed, 28 Sep 2005 18:02:30 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v733) In-Reply-To: <9e3862d805092816396bbd69fd@mail.gmail.com> References: <1127924669.30888.40.camel@echidna.inamo.no> <9e3862d805092816396bbd69fd@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <847C2ADC-41F9-4A1E-ADA2-F71326A8F5F6@gmail.com> Content-Transfer-Encoding: quoted-printable From: Kev Jackson Subject: Re: suggestion refactor SCM Date: Thu, 29 Sep 2005 08:02:01 +0700 To: "Ant Developers List" X-Mailer: Apple Mail (2.733) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 29 Sep 2005, at 06:39, Brett Porter wrote: > I'd also agree with that. We fully intended to make Maven2 plugins > work as Ant tasks :) > > So with a wrapper, > http://maven.apache.org/maven2/scm/maven-scm-plugin/ > these goals would become tasks and their parameters would match up > what's on the individual pages. > > Thoughts? Just a worry about dependencies. If Ant has to rely on other code =20 from within maven for a set of maven plugins to run, we end up with a =20= horrible interdependency (Maven needs Ant <-> Ant needs some % of =20 Maven) just to compile ant. Could get nasty. But I agree if the =20 work is there and the code can be taken and made common between =20 projects, why not? (When you first replied Brett, I checked out the source in svn web =20 thingy and I saw a fair bit of codehaus imports - I personally don't =20 have any good experience (as a user) of anything from codehaus so I'm =20= wary of that code, but you obviously have a more in depth view) > > - Brett > > On 9/29/05, Trygve Laugst=F8l wrote: > >> On Wed, 2005-09-28 at 16:56 +0100, Jose Alberto Fernandez wrote: >> >>>> From: Steve Loughran [mailto:stevel@apache.org] >>>> >>>> Jose Alberto Fernandez wrote: >>>> >>>>> But here we seem to be talking about a new family of generic =20 >>>>> tasks, >>>>> If this works well, we could deprecate the old tasks and =20 >>>>> eventually >>>>> >>> in a >>> >>>>> couple of versions remove them. >>>> My thoughts were that in the future you'd download a base-ant, and =20 then depending on the SCM you use you'd download the scm-provider-=20 ant.jar eg base-ant1.8.jar + svn-ant.jar Each antlib is going to be tiny compared to the amount you have to =20 download for all SCM functionality that we currently have (I'm still =20 on dial-up here so download speed and size of code is important to =20 me :) ) >>>> generic is good, provided >>>> -we can have a conceptual model that is consistent across all SCM >>>> systems. >>>> -we can deal with extensibility through antlibs. I suppose you'd >>>> >>> have >>> The hard part is defining a consistent interface which is applicable =20 to all SCM systems, without dropping down to lowest common denominator. Kev -- "In vain you tell me that Artificial Government is good, but that I =20 fall out with the Abuse. The Thing! The Thing itself is the Abuse!" - =20= Edmund Burke --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org