Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 54946 invoked from network); 9 Sep 2002 23:12:17 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 9 Sep 2002 23:12:17 -0000 Received: (qmail 10677 invoked by uid 97); 9 Sep 2002 23:12:55 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 10661 invoked by uid 97); 9 Sep 2002 23:12:55 -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 10648 invoked by uid 98); 9 Sep 2002 23:12:54 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <008c01c25857$74ea5af0$1219570f@ranier> From: "Steve Loughran" To: "Ant Developers List" References: <6D74CC7DB9535C4885A40FD962630458088F1B@phsormsg06.or.providence.org> Subject: Re: nantcall task (was: Optional task: Visual Basic.NET compile) Date: Mon, 9 Sep 2002 16:20:13 -0700 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-MailScanner: Found to be clean X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "Felder, Brian" To: "'Ant Developers List'" Sent: Monday, September 09, 2002 3:41 PM Subject: nantcall task (was: Optional task: Visual Basic.NET compile) > I like the approach of calling NAnt from Ant. Just out of curiosity, I built > a task. I'm attaching a first cut at this, with tests. It's > extremely simple: it takes a NAnt buildfile name, and a space-separated list > of targets. [NANT_HOME]/bin must be in the PATH for this to work. comma separated, surely. Spaces are valid in target names. > > I'm not sure if there are issues related to using this within Cruise > Control. If it works as Curt says, perhaps this would be a good way to have > Ant drive a build process that includes both Java and .NET code. > > Brian one thing that does is pass down references and properties, messages sent from below are passed up, things we have to replicate across processes. We have the same problem with as one would have with with fork=true, if that were ever implemented. The obvious solution here is (and its a good one) -define an XML wire protocol that can be used between an ant process and a sub process. -use that wire protocol over std-in and std-out, or over tcp loopback If done right, the same protocol would work for nant, ant w/ forking and remote access a la rant. SOAP would seem the obvious choice, though it doesnt have a stdio transport that I am aware of. -- To unsubscribe, e-mail: For additional commands, e-mail: