Actually, I do believe that it is mentioned in the manuals. Have you tried
adding a - before the target name. So -test will be an internal target.
I haven't tried this myself, however.
Regards
Sameer
-Original Message-
From: Marc Logemann [mailto:[EMAIL PROTECTED]]
Sent: Monday,
Here's some more on this from the Ant Manual:
The optional description attribute can be used to provide a one-line
description of this target, which is printed by the -projecthelp
command-line option. Targets without such a description are deemed internal
and will not be listed, unless either
There really is not an official or built-in way to do this, but you can
prepend a - to a target and that makes it invisible from the command-line
at least. I'm sure that other special characters, like a space, would do
the trick too. This is an unsupported hack though - so use at your own
risk.
f.y.i
http://marc.theaimsgroup.com/?l=ant-userm=99849430717822w=2
-Original Message-
From: Todd Chambery [mailto:[EMAIL PROTECTED]]
Sent: 01 November 2001 20:10
To: Ant Users List
Subject: private targets
Hi all,
I've noticed that, for organization's sake and code reuse,
On Fri, 2 Nov 2001 07:10, Todd Chambery wrote:
Hi all,
I've noticed that, for organization's sake and code reuse, I've created a
lot of dependent targets. These are essentially fragments common to
other targets for which it would make sense to run independently.
I'd like to make it so
On Thu, 1 Nov 2001, Todd Chambery wrote:
I'd like to make it so they could only be run when called from within the
buildfile (not when listed on the command line), thereby more tightly
controlling how my buildfile can be used. Is there any facility for doing
this?
Not really.
You can get
