Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ant-dev@jakarta.apache.org
From: "Jose Alberto Fernandez" <j_a_fernandez@yahoo.com>
To: <ant-dev@jakarta.apache.org>
Subject: RE: [ANN] Collecting requirements for Ant2
Date: Thu, 22 Mar 2001 23:47:53 -0000
Message-ID: <013e01c0b32a$837a1bb0$ef69883e@viquity.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <F68hCFQGKpRmDSimeat0000324a@hotmail.com>
Importance: Normal

> From: Charles Burdick [mailto:charles_burdick@hotmail.com]
> 
> Here's some thoughts on what I'd like to see in Ant2:
> 
> - Clean distinction between ant-core and ant-tasks, both in 
> codebase and 
> communication. I'd like to see the ant-dev list split into 2 
> mailing lists, 
> one for ant-core and one for ant-tasks.
> 
+1
> - Reduce the scope of the "built-in" tasks to those that are 
> essential, then 
> have a tiers of other tasks, like optional (endorsed by the ant-dev 
> community) and contrib (contributed, but not necessarily tested or
> standardized). How are Apache webserver modules or Perl 
> modeles managed?
> 
+1, but we need tasklibs for this to work well.

> - In ant-core, flesh out and strengthen interfaces that 
> standardize and 
> generalize most of the tasks in ant-tasks.
> 
+1
> - Use log4j rather than the custom logging found in Ant1 
> (this would allow 
> custom ant extensions to play nice with other custom libraries).
> 
+1
> Thanks,
> Chuck Burdick
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com
>