t;
> Unfortunately, there is no ascii characters after ~. Maybe starting the top
> level target by an uppercase and using _
> might work.
>
> Gilles
>
> > -Original Message-
> > From: mjdenham [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 21 novembre 20
> -Original Message-
> From: mjdenham [mailto:[EMAIL PROTECTED]
> Sent: mercredi 21 novembre 2007 12:57
> To: user@ant.apache.org
> Subject: Re: Specify non-top level target
>
>
> Thanks for all those great ideas everybody.
>
> Two ideas that I liked the most w
Thanks for all those great ideas everybody.
Two ideas that I liked the most were:
1. add a description to the target, making it non-internal. Then click the
"Hide Internal Targets" toolbar button in Eclipse ant View.
2. Use a special prefix for internal ant targets. The standard seems to be
'-
roup them logically, even when they have a
description.
Gilles
> -Original Message-
> From: Dominique Devienne [mailto:[EMAIL PROTECTED]
> Sent: mardi 20 novembre 2007 19:42
> To: Ant Users List
> Subject: Re: Specify non-top level target
>
> On Nov 20, 2007 12:24 PM,
-Original Message-
From: mjdenham [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 20, 2007 7:25 PM
To: user@ant.apache.org
Subject: Specify non-top level target
/*
My ant build file is getting quite long and has a lot of targets. When
I
view the ant file in Eclipse it can be difficu
When you create top level targets, use the "description" parameter.
Then, when you do ant -projecthelp, the names of the targets show up:
$ ant -projecthelp
Buildfile: build.xml
Main targets:
archive Builds the compressed tarball archive in directory "archive"
Default target: ???
$
Now thro
On Nov 20, 2007 12:24 PM, mjdenham <[EMAIL PROTECTED]> wrote:
> My ant build file is getting quite long and has a lot of targets. When I
> view the ant file in Eclipse it can be difficult to see which targets are
> the top-level ones which I would call and which are just helper targets like
> "ini
