Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: pass (athena.apache.org: domain of jeanlouis.boudart@gmail.com
 designates 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=NrB8wY2pXzkGABeNhC1UEXj4IGRpAN55ceO7bexPWHA3xcWMUmGFocM2TScibYS40Q
         EvkxBxe7/0BtZK/iid254LzltFZzJaWtaRcYszo7xNMoiZ5r4NahdeaeVRYjEL2aSiYv
         9k7+qQRRUKiUTbePwgnvi6fcmzIuaJS33ELBA=
Message-ID: <e802d55e0811280811v252b8075j193352558beb6d8f@mail.gmail.com>
Date: Fri, 28 Nov 2008 17:11:27 +0100
From: "Jean-Louis BOUDART" <jeanlouis.boudart@gmail.com>
To: "Ant Developers List" <dev@ant.apache.org>
Subject: Re: target-group committed
In-Reply-To: <255d8d690811261224t20eaab55q5676b44b8c20d3ec@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_42859_26927804.1227888687045"
References: <y1uljvfvq4w.fsf@v30161.1blu.de>
	 <e802d55e0811190527r78396a44oddcae474642a525c@mail.gmail.com>
	 <y1uljvf0y5b.fsf@v30161.1blu.de>
	 <635a05060811200025h557b43e7x25a80abc488e2821@mail.gmail.com>
	 <e802d55e0811200659pf2bbfebl473a448a543999ef@mail.gmail.com>
	 <492C5F75.4070502@callenish.com>
	 <e9d8a2610811260000g1b637fbah729af2fbb13f1142@mail.gmail.com>
	 <492DAC47.9090603@callenish.com>
	 <255d8d690811261224t20eaab55q5676b44b8c20d3ec@mail.gmail.com>

------=_Part_42859_26927804.1227888687045
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I'm +1 for this solution
2008/11/26 Dominique Devienne <ddevienne@gmail.com>

> On Wed, Nov 26, 2008 at 2:06 PM, Bruce Atherton <bruce@callenish.com>
> wrote:
> > Or you could just live with the verbosity of the target list, like I did,
> > and use naming conventions in EasyAnt. I'm sure there are many other ways
> to
> > address the issue.
>
> One possible way would be to provide an in-build-file hook to
> intercept the -p switch, and this hook (I envision a target) would
> then be responsible to display the help. Couple that with a new
> configurable task to generate the -p output, and then it's up to the
> user to select (via some kind of include/exclude) whatever targets are
> going to be listed.
>
> My builds used to all have a help target which <java>'d back into Ant
> on the same build file with the -p switch added. It's the same idea,
> but exposing a builtin task instead, and allowing to run that target
> when -p is specified, if it's hooked via for example a <project
> help-target="help">.
>
> --DD
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>

------=_Part_42859_26927804.1227888687045--