Added: ant/core/trunk/docs/manual/targets.html
+
+ pTargets can depend on other targets and Ant ensures that these
+other targets have been executed before the current target. For
+example you might have a target for compiling, for example, and a
I deleted the 2nd example.
+ pIt is
On Mon, 21 Dec 2009 14:00:53 -0500, Sandu Turcan atur...@gmail.com
wrote:
On the other hand the term extension point sounds generic and appears
to accept anything the system operates on, like tasks, types, targets,
dependencies etc.
In this case we're only talking about targets.
I think a
On 2009-12-22, jan.mate...@rzf.fin-nrw.de wrote:
Added: ant/core/trunk/docs/manual/targets.html
pTargets can depend on other targets and Ant ensures that these
other targets have been executed before the current target. For
example you might have a target for compiling, for example,
On 2009-12-18, Stefan Bodewig bode...@apache.org wrote:
The Incubator IP-CLEARANCE process has entered its final stage,
I've closed the vote (no responses at all) at the incubator, it has
passed.
Nicolas, feel free to import the Groovy-Front into the sandbox whenever
you feel like it.
Stefan
On 2009-12-18, Stefan Bodewig bode...@apache.org wrote:
If I'd be the one to create the release, I'll need some help by Kev
and/or Antoine to become able to compile the optional tasks with
commercial dependencies. That being said, if Antoine wants to take
things over, I'll happily let him do
resending a mail which was considered spam by the ezmlm program
Stefan Bodewig wrote:
On 2009-12-18, Stefan Bodewig bode...@apache.org wrote:
If I'd be the one to create the release, I'll need some help by Kev
and/or Antoine to become able to compile the optional tasks with
commercial
Stefan Bodewig wrote:
On 2009-12-18, Stefan Bodewig bode...@apache.org wrote:
If I'd be the one to create the release, I'll need some help by Kev
and/or Antoine to become able to compile the optional tasks with
commercial dependencies. That being said, if Antoine wants to take
things over,
Hi,
I would like to start a formal vote on the name of target-group.
[ ] target-group name=foo/ for the group and target group=foo ...
for the members of the group
this is the current codebase
[ ] extension-point name=foo/ for the group and target
extensionOf=foo ... for members of the
Antoine Levy Lambert wrote:
[ x] target-group name=foo/ for the group and target group=foo
... for the members of the group
this is the current codebase
Let me start with +1 for the current codebase.
Antoine
-
To
[ x] extension-point name=foo/ for the group and target
extensionOf=foo ... for members of the group
or as an alternative
[ x] target-interface name=foo/ for the group and target
implements=foo ... for the members of the group
2009/12/22 Antoine Levy Lambert anto...@gmx.de
Antoine Levy Lambert
On 2009-12-22, Steve Loughran ste...@apache.org wrote:
I'd better make sure all my funtest stuff is documented then, hadn't I
If you want it as part of 1.8.0, yes, better hurry up.
I have removed it from defaults.properties, BTW.
Stefan
You're right.
Initially in EasyAnt we wanted to find a way to define lifecycles. A
lifecycle is composed by a sequence of generic steps (what we've called
phase).
Then we could play with additional script (plugins) that can be bind to a
phase.
Again the idea was to make genericity in our build
On 2009-12-22, Antoine Levy Lambert anto...@gmx.de wrote:
I would like to start a formal vote on the name of target-group.
Currently I don't have strong feelings either way, I prefer
extension-point slightly, but can certainly live with target-group.
I'll go with the majority.
[ ]
Thanks Jesse
Jan
URL: http://svn.apache.org/viewvc?rev=893210view=rev
Log:
Typo.
-tasks direclty under the project tag (since Ant 1.6.0):/p
+tasks directly under the project tag (since Ant 1.6.0):/p
blockquotepre
14 matches
Mail list logo
