Return-Path: 
 <user-return-62253-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 81826 invoked from network); 18 Sep 2007 14:58:29 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 18 Sep 2007 14:58:29 -0000
Received: (qmail 47755 invoked by uid 500); 18 Sep 2007 14:58:17 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 47732 invoked by uid 500); 18 Sep 2007 14:58:17 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 47721 invoked by uid 99); 18 Sep 2007 14:58:17 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 07:58:17 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ddevienne@gmail.com
 designates 66.249.92.173 as permitted sender)
Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 14:58:16 +0000
Received: by ug-out-1314.google.com with SMTP id c2so92569ugf
        for <user@ant.apache.org>; Tue, 18 Sep 2007 07:57:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=mhw+2yTGjZi3Rc9Ih8sORDsjX6kpnrt7y3b/eDygXEY=;
        b=k743J2eMam9mIX8K5Bzl4G+OAu/byAmnGec1D3v5uO5D80uZkgH53O/V+6L3YCYEhZNg0Xp5Mk8ZYW4KBDzuFx2AaqPLLXOXM6QdPMRC3ANFKPcc2CmsoVKGldJ8KU9jjONeipHnT3KNvBpN6uEXH7CQN1etQhgBresMFOKvLTM=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=F86ksZSPo1qmxg5UOSRnX8xKLCbBcos2/vUY+ZwVtcCSc9PYQRbV7JFzJ//c5+ft1Naa+R4vMD4T34lCZj4rwK9DLPDxUM4yVWIy4cFJcTOGEOCRHRYYmvmuE3z+rujtyQQZzEZvHCtZP1KKMaD45GW5eiBc9oxDoGKBOJ9L6JU=
Received: by 10.66.225.17 with SMTP id x17mr814039ugg.1190127474458;
        Tue, 18 Sep 2007 07:57:54 -0700 (PDT)
Received: by 10.66.248.7 with HTTP; Tue, 18 Sep 2007 07:57:54 -0700 (PDT)
Message-ID: <255d8d690709180757n10cb313cr61fdb0dae1a7a5ad@mail.gmail.com>
Date: Tue, 18 Sep 2007 09:57:54 -0500
From: "Dominique Devienne" <ddevienne@gmail.com>
To: "Ant Users List" <user@ant.apache.org>
Subject: Re: adding a fork option to my ant task
In-Reply-To: <46EFE6E4.4000600@gmx.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46EFC18D.1020604@gmx.org>
	 <255d8d690709180724g537fc4d0q596f61660c2475aa@mail.gmail.com>
	 <46EFE6E4.4000600@gmx.org>
X-Virus-Checked: Checked by ClamAV on apache.org

> > Use <java> in your code rather than in the build file. It's easy use a
> > helper task in a task, with the bindToOwner call (not sure of the
> > name). I've used this technique in the past, and it works well. The
> > technique does assume you have a command line entry point rich-enough
> > to specify exactly what you want done entirely on the command line.
>
> then I take it there is no simple way for this...  then I have to find
> out, how to get the classpath from the taskdef :(

Actually, no. One of the great advantage of composing a forking <java>
task is that it no longer requires the Ant task itself to depend on
the forked program classes (Groovyc in this case).

The task allows to present a nice front-end to specify in a nice Ant
way (using filesets, etc...) what you want to do, package that up into
a long an ugly command line, and fork that away. The Task itself
become Groovyc-dependency free.

I usually explicitly expose a task element to specify explicitly the
classpath to use to locate the Groovy classes, and whatever it depends
on. You thus no longer have to mix the Ant classpath with the forked
program's classpath, which is very very useful IMHO.

--DD

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org