Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 81154 invoked from network); 23 May 2002 09:06:59 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 May 2002 09:06:59 -0000 Received: (qmail 23664 invoked by uid 97); 23 May 2002 09:07:08 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 23648 invoked by uid 97); 23 May 2002 09:07:08 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 23636 invoked by uid 98); 23 May 2002 09:07:07 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-ID: <00e101c20239$31539d70$6401a8c0@darden.virginia.edu> From: "Erik Hatcher" To: "Ant Developers List" References: <065801c201d4$5dd0ba50$9865fea9@spiritsoft.com> Subject: Re: exporting classpath references from inner Ant builds to outer Ant builds. Date: Thu, 23 May 2002 05:06:57 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N This sounds kinda risky in that a sub-build could stomp on properties (I assume you'd want those exported back up too?) and references that you did expect to be altered. Do you envision any mechanisms for controlling what gets exported? All references blindly? Or some selection mechanism? ----- Original Message ----- From: "James Strachan" To: Sent: Wednesday, May 22, 2002 5:05 PM Subject: exporting classpath references from inner Ant builds to outer Ant builds. > I'm moving various projects to Maven at the moment. One feature that'd make > my life much easier is if I could call Maven's Ant build file to compile > some stuff and generate the classpath to use to run sample programs using > its project.xml dependency information, then for this generated classpath to > be exported back to me for use in an outer build. > > e.g. imagine if my projects build file looked like this... > > > > > > > > > > > > > > > > > > > > > > > > This is kinda the opposite way around for the targets > inheritRefs="true" - I guess I want to be able to use an exportRefs="true" > for references to be exported from the called Ant project to the calling Ant > project. This feature would also help making the Maven plugins a bit easier > too I should think. > > Anyone any comments on whether this seems reasonable or if I've missed > something? I'm happy to investigate further and have a go at creating a > patch for Ant; I'd just like a sanity check before I head off in this > direction. > > James > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > -- > To unsubscribe, e-mail: > For additional commands, e-mail: > > -- To unsubscribe, e-mail: For additional commands, e-mail: