Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 73271 invoked from network); 14 Nov 2007 16:52:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Nov 2007 16:52:26 -0000 Received: (qmail 38909 invoked by uid 500); 14 Nov 2007 16:52:13 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 38857 invoked by uid 500); 14 Nov 2007 16:52:13 -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 38846 invoked by uid 99); 14 Nov 2007 16:52:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2007 08:52:13 -0800 X-ASF-Spam-Status: No, hits=-6.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of whaefelinger@epo.org designates 145.64.132.100 as permitted sender) Received: from [145.64.132.100] (HELO gvmail01.epo.nl) (145.64.132.100) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Nov 2007 16:52:01 +0000 Received: from localhost (localhost [127.0.0.1]) by gvmail01.epo.nl (Postfix) with ESMTP id 74A323E391 for ; Wed, 14 Nov 2007 17:51:52 +0100 (CET) X-Virus-Scanned: scanned at epo.org Received: from mail01.internal.epo.org (mail01.internal.epo.org [10.0.2.89]) by gvmail01.epo.nl (Postfix) with ESMTP id E4A383E392 for ; Wed, 14 Nov 2007 17:51:50 +0100 (CET) In-Reply-To: <255d8d690711140839k2269705dqb5ba476afa335d3d@mail.gmail.com> To: "Ant Developers List" Subject: Re: ApacheCon Presentation MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0.2 HF698 July 11, 2007 From: =?ISO-8859-1?Q?Wolfgang_H=E4felinger?= Message-ID: Date: Wed, 14 Nov 2007 17:51:48 +0100 X-MIMETrack: Serialize by Router on Mail01/EPO(Release 7.0.2|September 26, 2006) at 14-11-2007 17:51:50, Serialize complete at 14-11-2007 17:51:50 Content-Type: multipart/alternative; boundary="=_alternative 005CA28CC1257393_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 005CA28CC1257393_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable >> Then again it's these people, Peter first, who enhance Ant to=20 >> support better models for the future, so power to you guys ;-) Cool, so we can expect 'auto-download' to be a feature of 1.7.1? Serious, just to pull off some kind of demo implementation: is there some=20 kind of=20 namespace interceptor in Ant's source code? I'm just asking cause I have=20 never seen such a beast... Regards, Wolfgang H=E4felinger Research & Architecture | Dir. 2.7.0.2 European Patent Office Patentlaan 3-9 | 2288 EE Rijswijk | The Netherlands Tel. +31 (0)70 340 4931 whaefelinger@epo.org http://www.epo.org "Dominique Devienne" =20 14-11-2007 17:40 Please respond to "Ant Developers List" To "Ant Developers List" cc Subject Re: ApacheCon Presentation On Nov 14, 2007 9:50 AM, Peter Reilly wrote: > On Nov 14, 2007 3:18 PM, Dominique Devienne wrote: > > On Nov 14, 2007 8:07 AM, Wolfgang H=E4felinger =20 wrote: > > > * Simple fix...place all third-party jars in $ANT=5FHOME/lib > > > > > > Honestly, putting something into Ant's lib directory is really ugly = and all > > > those alternatives ($HOME/.ant etc) do not solve the overall=20 problem. > > I would argue that using -lib is nearly as ugly as placing jars in=20 $ANT=5FHOME/lib > (but not as bad!!) > > On projects at work, that I am involved in, I insist on > using "clean room" ant 1.7.0 and "clean room" java 1.5.* (or higher). > > For each antlib / extension that is needed, I have an ant file that > sets up the extension for-example ant-contrib. Given a corporate environment (as opposed to OSS), I believe it's entirely OK, and even A-Good-ThingTM to have an official and properly configured Ant version which is the only *official* and *sanctioned* way to run the builds, which is under source control. The allows proper control of the dependencies, and allows to manage Ant versions to be used by the different branches/versions of the software, and most importantly it's easy! Check out the proper branch of the build tools, and of the software to be built, and you're in business. Just add JDK and shake, and here you go, instant CM ;-) I'm sure your build organization rocks Peter, but I personally view it as more complex and more trouble that I was willing to live with myself (I'm not even sure I could pull such a setup off myself in fact!). Different people draw the line between the absolute ideal and the practical at different places. Having a centralized Ant under SCM was the thing for me, and obviously others find it unacceptable, and have to live with my complex setups. Then again it's these people, Peter first, who enhance Ant to support better models for the future, so power to you guys ;-) Cheers, --DD --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org --=_alternative 005CA28CC1257393_=--