Hello,
I have build a large automatic and generic build system using ANT.
This build system got very complex, especially due to dependencies.
I definitly do like the before/after approach, but the already
suggested depends usage will add another step of complexity.
Furthermore, up until now, I thought, that there is no guarantee, in
which order the depends targets will be executed, am I wrong here?
R,
Markus
Zitat von Dominique Devienne <[EMAIL PROTECTED]>:
On 1/14/08, Wolfgang Häfelinger <[EMAIL PROTECTED]> wrote:
> Q1: Does everyone agree that adding before/after to target to Ant 1.8
> is useful and should be done before (in conjunction of) creating
> generic build files?
could you please explain why you see a need for target attributes "before"
and "after" rather than following the Macro path I proposed?
I guess because I think in terms of targets and not macros. I've used
macros, but to define new "tasks", not to control the structure of the
build itself. For that, targets and dependencies are the building
blocks IMHO.
At this point I don't understand the macro approach that you advocate,
and even if it worked, I'd argue that it may not be the "natural" way
to add the flexibility we have been discussing about. Could very well
be that I'm wrong, but at this point it's my thinking.
The fact that your macro approach to extensibility works without
changes to Ant is nice but not a strong-enough point to me, if it
feels less natural that the before/after target approach that would
require changes in Ant. I.e. I care more about the user friendliness
and doing it in a simple and natural way, than the implementation
details. --DD
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
----- Ende der weitergeleiteten Nachricht -----
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
