We comment (with descriptions) all targets. Descriptions for targets
that are not public are there for build file maintenance. However, we
could always just remove descriptions and put them in as XML comments I
guess. But this conversation's really for a different forum now!
Phil :n)
On Thu,
Agreed,
This should be done in ant 1.7.
Relying on dashes and descriptions for visiblity
of targets is wrong.
Peter
On Friday 26 September 2003 09:43, Phil Weighill-Smith wrote:
We comment (with descriptions) all targets. Descriptions for targets
that are not public are there for build file
From: Gus Heck [mailto:[EMAIL PROTECTED]
How does a java application (other than ant) invoke an ant
target (I
can see using a task easily, but not a target) Can you give me an
example where a target gets invoked by java code?
Well there is the callTarget() method, but nevermind
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23397.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Since bug 22020 has been duped twice (once before, and once since) and
there is a patch available (mine of course :), though I did not report
22020), what are the chances of geting it into 1.6 It was submitted
months ago.
-Gus
[EMAIL PROTECTED] wrote:
DO NOT REPLY TO THIS EMAIL, BUT PLEASE
[Bug 23397] - Need attribute for target tag to
indicate hidden/internal target
Since bug 22020 has been duped twice (once before, and once since) and
there is a patch available (mine of course :), though I did not report
22020), what are the chances of geting it into 1.6 It was submitted
months
Antoine Levy-Lambert wrote:
What you would like would be useful to prevent the wrong targets from
being called. But I wonder whether this change would not make ant
unnecessary complex.
The default (atribute omitted) state should behave as always. This is
necessary for back compatability, and
In fact I would be even more interested to hear the opinons of both
commiters and non-commiters :).
-Gus
Gus Heck wrote:
Antoine Levy-Lambert wrote:
What you would like would be useful to prevent the wrong targets from
being called. But I wonder whether this change would not make ant
unnecessary
Developers List
Subject: Re: AW: DO NOT REPLY [Bug 23397] - Need attribute for target
tag to indicate hidden/internal target
In fact I would be even more interested to hear the opinons of both
commiters and non-commiters :).
-Gus
Gus Heck wrote:
Antoine Levy-Lambert wrote:
What
applications.
Jan
-Original Message-
From: Gus Heck [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 5:58 PM
To: Ant Developers List
Subject: Re: AW: DO NOT REPLY [Bug 23397] - Need attribute for target
tag to indicate hidden/internal target
In fact I would
: AW: DO NOT REPLY [Bug 23397] - Need attribute for target
tag to indicate hidden/internal target
This attribute would be rather handy for tools such as IntelliJ IDEA
which allows the graphical display of available targets for invocation
(within its Ant integration). It would be great if IDEA
work too, if invoked by other java
applications.
Jan
-Original Message-
From: Gus Heck [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2003 5:58 PM
To: Ant Developers List
Subject: Re: AW: DO NOT REPLY [Bug 23397] - Need attribute for target
tag to indicate hidden/internal target
How does a java application (other than ant) invoke an ant
target (I
can see using a task easily, but not a target) Can you give me an
example where a target gets invoked by java code?
Never done for myself. But this is often asked on the list (and answered).
- instantiate Project
-
This is something to consider for ant 1.7 and not for 1.6.
Personally I cannot see the need for it, but then I try
to have as few non user level targets as possible.
Pete
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23397.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Phil Weighill-Smith wrote:
This attribute would be rather handy for tools such as IntelliJ IDEA
which allows the graphical display of available targets for invocation
(within its Ant integration). It would be great if IDEA could know which
targets are entry points to the build file and only
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23397.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
17 matches
Mail list logo
