Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
From: "Thomas Christen" <chr@active.ch>
To: <ant-dev@jakarta.apache.org>
Subject: RE: [PATCH] Nested Tasks
Date: Tue, 13 Mar 2001 21:43:32 +0100
Message-ID: <00ac01c0abfe$4456dc80$2101a8c0@chr2>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <3.0.6.32.20010201142530.008eb140@alphalink.com.au>
Importance: Normal

Tanks for all your comments about parallelism and whether to allow nested
tasks or not. I feel that most of you are against my proposed concepts. OK

In our company we have build a larger amount of jobs using very intensive
the new parallel, wait and the newly written queue tasks. Looking back -
with the help of these new concepts the build-files are very readable and
the nested tasks approach allows an easy and intuitive understanding what's
going on.

Having done the same with added properties like async="true" and all the
"MUST NOT async", "MUST async" and "MAY async" stuff the logic would be
hidden and it would be very difficult to see the red line through the build
dependencies.

The mentioned complexity for task writers - I cant see this point. The only
thing a task writer has to do is inherit Task. The problem of concurrent
output - witch has to be solved in any concepts - is done by the Container
(e.g. parallel).

Please forgive me for this additional comment on this dead topic and let me
say thank you to all the good stuff in ant provided by many people.

Regards
Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: ant-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: ant-dev-help@jakarta.apache.org